[FFmpeg-devel] [PATCH] doc/ffmpeg: Document VAAPI device creation options

[Mark Thompson]

---
 doc/ffmpeg.texi | 28 ++++++++++++++++++++++++++--
 1 file changed, 26 insertions(+), 2 deletions(-)

diff --git a/doc/ffmpeg.texi b/doc/ffmpeg.texi
index cd35eb49c8..ccd490d1a7 100644
--- a/doc/ffmpeg.texi
+++ b/doc/ffmpeg.texi
@@ -950,8 +950,32 @@ device type:
 
 @item vaapi
 @var{device} is either an X11 display name or a DRM render node.
-If not specified, it will attempt to open the default X11 display (@emph{$DISPLAY})
-and then the first DRM render node (@emph{/dev/dri/renderD128}).
+If not specified, it will attempt to open the first usable DRM render node
+(@emph{/dev/dri/renderD128}, @emph{/dev/dri/renderD129}, etc.).  If no render
+node is found then it will try the default X11 display (@emph{$DISPLAY}).
+
+Some options are also supported to guide the selection:
+ at table @option
+ at item connection_type
+Explicitly specify the connection type to use - @samp{x11} or @samp{drm}.
+ at item kernel_driver
+Only consider DRM render nodes using the named kernel driver.
+ at item driver
+Select the VA driver to load after the connection is open.  This does not
+affect the selection of the device itself.
+ at end table
+
+Examples:
+ at table @emph
+ at item -init_hw_device vaapi:/dev/dri/renderD129
+Choose the device on the second DRM render node.
+ at item -init_hw_device vaapi:,connection_type=drm,kernel_driver=amdgpu
+Choose a device on a DRM render node using the @emph{amdgpu} kernel driver,
+as found on most current AMD graphics devices.
+ at item -init_hw_device vaapi:,kernel_driver=i915,driver=iHD
+Choose a device using the @emph{i915} kernel driver, and load the @emph{iHD}
+VA driver to use with it.
+ at end table
 
 @item vdpau
 @var{device} is an X11 display name.
-- 
2.20.1