From: Hendrik Leppkes <h.leppkes@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] Add support d3d11va Intel Hevc Rext decoder.
Date: Sun, 25 Feb 2024 16:46:38 +0100
Message-ID: <CA+anqdyYOGX=QMDidewhs6LUJyRnr4rLA+9KKiEDevXvGFY+VA@mail.gmail.com> (raw)
In-Reply-To: <a087150b-3d13-410d-ac2a-d9b054e3ec45@jkqxz.net>
On Sun, Feb 25, 2024 at 11:36 AM Mark Thompson <sw@jkqxz.net> wrote:
>
> On 25/02/2024 02:22, Водянников А.В. via ffmpeg-devel wrote:
> > From ed8fda62bbdbc62f7565891c935966c931d001ca Mon Sep 17 00:00:00 2001
> > From: Aleksoid <Aleksoid1978@mail.ru>
> > Date: Thu, 22 Feb 2024 19:15:48 +1000
> > Subject: [PATCH 1/2] Add support d3d11va Intel Hevc Rext decoder.
> >
> > Signed-off-by: Aleksoid <Aleksoid1978@mail.ru>
> > ---
> > libavcodec/d3d12va_hevc.c | 2 +-
> > libavcodec/dxva2.c | 68 +++++++++++++++++++++++++++++++++--
> > libavcodec/dxva2_hevc.c | 41 ++++++++++++++++++---
> > libavcodec/dxva2_internal.h | 38 +++++++++++++++++++-
> > libavcodec/hevcdec.c | 16 +++++++++
> > libavutil/hwcontext_d3d11va.c | 26 +++++++++++---
> > 6 files changed, 178 insertions(+), 13 deletions(-)
>
> What elements are Intel-specific about this?
>
> Presumably there will be an official rext mode for D3D in future; are there any possible problems with having this vendor extension in that case?
>
The next Windows SDK is presumably supposed to contain RExt support,
but so far only partial information is present in the pre-release
SDKs. It might be wise to wait for that.
- Hendrik
_______________________________________________
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-02-25 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 2:22 Водянников А.В. via ffmpeg-devel
2024-02-25 10:36 ` Mark Thompson
2024-02-25 15:46 ` Hendrik Leppkes [this message]
2024-02-25 21:55 ` Александр Водянников via ffmpeg-devel
2024-02-25 23:35 ` Александр Водянников via ffmpeg-devel
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='CA+anqdyYOGX=QMDidewhs6LUJyRnr4rLA+9KKiEDevXvGFY+VA@mail.gmail.com' \
--to=h.leppkes@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