From: Dennis Mungai <dmngaie@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 1/2] doc/ffmpeg: update the documentation about qsv device creation Date: Tue, 2 Jan 2024 19:00:58 +0300 Message-ID: <CAKKYfmEx4FovznJ4VCpwercdc8rQuGDDW4Q391buvWvv5mz1WA@mail.gmail.com> (raw) In-Reply-To: <420e30d448519c2ea033a07b67888ebae83c857d.camel@intel.com> On Tue, 2 Jan 2024, 08:27 Xiang, Haihao, < haihao.xiang-at-intel.com@ffmpeg.org> wrote: > On Vr, 2023-12-29 at 12:23 +0800, Xiang, Haihao wrote: > > From: Haihao Xiang <haihao.xiang@intel.com> > > > > Signed-off-by: Haihao Xiang <haihao.xiang@intel.com> > > --- > > doc/ffmpeg.texi | 21 +++++++++++++++++++-- > > 1 file changed, 19 insertions(+), 2 deletions(-) > > > > diff --git a/doc/ffmpeg.texi b/doc/ffmpeg.texi > > index ab17d1d687..c6c0606e8a 100644 > > --- a/doc/ffmpeg.texi > > +++ b/doc/ffmpeg.texi > > @@ -1406,16 +1406,33 @@ If not specified, @samp{auto_any} is used. > > platform-appropriate subdevice (@samp{dxva2} or @samp{d3d11va} or > > @samp{vaapi}) and then deriving a > > QSV device from that.) > > > > -Alternatively, @samp{child_device_type} helps to choose > platform-appropriate > > subdevice type. > > -On Windows @samp{d3d11va} is used as default subdevice type. > > +The following options are recognized: > > +@table @option > > +@item child_device > > +Specify a DRM render node on Linux or DirectX adapter on Windows > > +@item child_device_type > > +Choose platform-appropriate subdevice type. On Windows @samp{d3d11va} > is used > > +as default subdevice type. > > +@end table > > > > Examples: > > @table @emph > > +@item -init_hw_device qsv:hw,child_device=/dev/dri/renderD129 > > +Create a QSV device with @samp{MFX_IMPL_HARDWARE} on DRM render node > > /dev/dri/renderD129 > > + > > +@item -init_hw_device qsv:hw,child_device=1 > > +Create a QSV device with @samp{MFX_IMPL_HARDWARE} on DirectX adapter 1. > The > > subdevice > > +type is @samp{d3d11va} if @code{--enable-libvpl} is specified at > > configuration time, the > > +subdevice type is @samp{dxva2} if @code{--enable-libmfx} is specified at > > configuration time. > > + > > @item -init_hw_device qsv:hw,child_device_type=d3d11va > > Choose the GPU subdevice with type @samp{d3d11va} and create QSV device > with > > @samp{MFX_IMPL_HARDWARE}. > > > > @item -init_hw_device qsv:hw,child_device_type=dxva2 > > Choose the GPU subdevice with type @samp{dxva2} and create QSV device > with > > @samp{MFX_IMPL_HARDWARE}. > > + > > +@item -init_hw_device qsv:hw,child_device=1,child_device_type=d3d11va > > +Create a QSV device with @samp{MFX_IMPL_HARDWARE} on DirectX adapter 1 > with > > subdevice type @samp{d3d11va} > > @end table > > > > @item opencl > > Will apply the patchset > A small request: The docs mention the creation of either VAAPI or d3d11 devices and then deriving a Quicksync device from that. Can your patchset include a trivial example of that, preferably with hwmap? That would eliminate the ambiguity in that clause. > _______________________________________________ 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:[~2024-01-02 16:01 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-29 4:23 Xiang, Haihao 2023-12-29 4:23 ` [FFmpeg-devel] [PATCH 2/2] doc/ffmpeg: update the documentation about vaapi " Xiang, Haihao 2024-01-02 5:26 ` [FFmpeg-devel] [PATCH 1/2] doc/ffmpeg: update the documentation about qsv " Xiang, Haihao 2024-01-02 16:00 ` Dennis Mungai [this message] 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=CAKKYfmEx4FovznJ4VCpwercdc8rQuGDDW4Q391buvWvv5mz1WA@mail.gmail.com \ --to=dmngaie@gmail.com \ --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