From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org> To: ffmpeg-devel@ffmpeg.org Cc: Haihao Xiang <haihao.xiang@intel.com> Subject: [FFmpeg-devel] [PATCH 2/2] doc/ffmpeg: update the documentation about vaapi device creation Date: Fri, 29 Dec 2023 12:23:58 +0800 Message-ID: <20231229042358.3703640-2-haihao.xiang@intel.com> (raw) In-Reply-To: <20231229042358.3703640-1-haihao.xiang@intel.com> From: Haihao Xiang <haihao.xiang@intel.com> Signed-off-by: Haihao Xiang <haihao.xiang@intel.com> --- doc/ffmpeg.texi | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/doc/ffmpeg.texi b/doc/ffmpeg.texi index c6c0606e8a..2c04b22cf3 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. +@end table + +Examples: +@table @emph +@item -init_hw_device vaapi +Create a vaapi device on the default device + +@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 + @item vdpau @var{device} is an X11 display name. If not specified, it will attempt to open the default X11 display (@emph{$DISPLAY}). -- 2.34.1 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-12-29 4:24 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-29 4:23 [FFmpeg-devel] [PATCH 1/2] doc/ffmpeg: update the documentation about qsv " Xiang, Haihao 2023-12-29 4:23 ` Xiang, Haihao [this message] 2024-01-02 5:26 ` Xiang, Haihao 2024-01-02 16:00 ` Dennis Mungai 2024-01-05 3:01 ` Xiang, Haihao
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20231229042358.3703640-2-haihao.xiang@intel.com \ --to=haihao.xiang-at-intel.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=haihao.xiang@intel.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git