From: Gyan Doshi <ffmpeg@gyani.pro> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 2/3] doc/ffmpeg: Update the description about d3d11va Date: Fri, 24 Nov 2023 11:25:39 +0530 Message-ID: <26f0927f-130c-40a1-98c8-42652dbefee8@gyani.pro> (raw) In-Reply-To: <20231124054348.3115276-2-haihao.xiang@intel.com> On 2023-11-24 11:13 am, Xiang, Haihao wrote: > From: Haihao Xiang<haihao.xiang@intel.com> > > Signed-off-by: Haihao Xiang<haihao.xiang@intel.com> > --- > doc/ffmpeg.texi | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) > > diff --git a/doc/ffmpeg.texi b/doc/ffmpeg.texi > index 68363ae045..5296b75a4e 100644 > --- a/doc/ffmpeg.texi > +++ b/doc/ffmpeg.texi > @@ -1165,6 +1165,21 @@ Choose the first device and use the primary device context. > > @item d3d11va > @var{device} is the number of the Direct3D 11 display adapter. > +If not specified, it will attempt to use the default Direct3D 11 display adapter > +or the first Direct3D 11 display adapter whose Harware VendorId is specified s/Harware/Hardware here and elsewhere. Regards, Gyan > +by @samp{vendor_id}. > + > +Examples: > +@table @emph > +@item -init_hw_device d3d11va > +Create a d3d11va device on the default Direct3D 11 display adapter. > + > +@item -init_hw_device d3d11va:1 > +Create a d3d11va device on the Direct3D 11 display adapter specified by index 1. > + > +@item -init_hw_device d3d11va:,vendor_id=0x8086 > +Create a d3d11va device on the first Direct3D 11 display adapter whose Harware VendorId is 0x8086. > +@end table > > @item vaapi > @var{device} is either an X11 display name, a DRM render node or a DirectX adapter index. _______________________________________________ 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-11-24 5:55 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-24 5:43 [FFmpeg-devel] [PATCH 1/3] lavu/hwcontext_d3d11va: Add option vendor_id Xiang, Haihao 2023-11-24 5:43 ` [FFmpeg-devel] [PATCH 2/3] doc/ffmpeg: Update the description about d3d11va Xiang, Haihao 2023-11-24 5:55 ` Gyan Doshi [this message] 2023-11-24 6:20 ` Xiang, Haihao 2023-11-24 5:43 ` [FFmpeg-devel] [PATCH 3/3] lavu/hwcontext_qsv: Make sure hardware vendor is Intel for qsv on d3d11va Xiang, Haihao 2023-11-26 10:51 ` Anton Khirnov 2023-11-27 2:33 ` Xiang, Haihao 2023-11-26 10:49 ` [FFmpeg-devel] [PATCH 1/3] lavu/hwcontext_d3d11va: Add option vendor_id Anton Khirnov 2023-11-27 1:57 ` 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=26f0927f-130c-40a1-98c8-42652dbefee8@gyani.pro \ --to=ffmpeg@gyani.pro \ --cc=ffmpeg-devel@ffmpeg.org \ /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