On date Friday 2024-01-05 10:33:52 +0800, Xiang, Haihao wrote:
> From: Haihao Xiang <haihao.xi...@intel.com>
>
> Signed-off-by: Haihao Xiang <haihao.xi...@intel.com>
> ---
> doc/ffmpeg.texi | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/doc/ffmpeg.texi b/doc/ffmpeg.texi
> index f095f402bd..8fb165c5df 100644
> --- a/doc/ffmpeg.texi
> +++ b/doc/ffmpeg.texi
> @@ -1385,6 +1385,29 @@ If not specified, it will attempt to open the default
> X11 display (@emph{$DISPLA
> and then the first DRM render node (@emph{/dev/dri/renderD128}), or the
> default
> DirectX adapter on Windows.
>
> +The following options are recognized:
> +@table @option
> +@item kernel_driver
> +When @var{device} is not specified, use this option to specify the name of
> the kernel
> +driver associated with the desired device. This option is only available when
> +@emph{libdrm} works on Linux.
Optional: might be good to specify a method to verify this condition.
> +@end table
> +
> +Examples:
> +@table @emph
> +@item -init_hw_device vaapi
> +Create a vaapi device on the default device
missing final dot here and below
> +
> +@item -init_hw_device vaapi:/dev/dri/renderD129
> +Create a vaapi device on DRM render node /dev/dri/renderD129
> +
> +@item -init_hw_device vaapi:1
> +Create a vaapi device on DirectX adapter 1
> +
> +@item -init_hw_device vaapi:,kernel_driver=i915
> +Create a vaapi device on a device associated with kernel driver @samp{i915}
> +@end table
> +
Looks good otherwise (but again, since hwaccels are probably
independent from ffmpeg they should be probably moved to a dedicated
manual).
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
