From: Mark Thompson <sw@jkqxz.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] libavutil/hwcontext_vaapi: Add a new nv12 format map to support vulkan frame
Date: Mon, 27 Dec 2021 18:56:48 +0000
Message-ID: <bfb77f48-26eb-69a2-8b1f-d73323ee7315@jkqxz.net> (raw)
In-Reply-To: <20211210160501.929C341050D@natalya.videolan.org>
On 10/12/2021 16:05, Wenbin Chen wrote:
> ffmpeg | branch: master | Wenbin Chen <wenbin.chen@intel.com> | Tue Dec 7 17:05:50 2021 +0800| [f3c9847c2754b7a43eb721c95e356a53085c2491] | committer: Lynne
>
> libavutil/hwcontext_vaapi: Add a new nv12 format map to support vulkan frame
>
> Vulkan will map nv12 to R8 and GR88, so add this map to vaapi to support
> vulkan frame.
>
> Signed-off-by: Wenbin Chen <wenbin.chen@intel.com>
>
>> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=f3c9847c2754b7a43eb721c95e356a53085c2491
> ---
>
> libavutil/hwcontext_vaapi.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/libavutil/hwcontext_vaapi.c b/libavutil/hwcontext_vaapi.c
> index 75acc851d6..994b744e4d 100644
> --- a/libavutil/hwcontext_vaapi.c
> +++ b/libavutil/hwcontext_vaapi.c
> @@ -992,6 +992,7 @@ static const struct {
> } vaapi_drm_format_map[] = {
> #ifdef DRM_FORMAT_R8
> DRM_MAP(NV12, 2, DRM_FORMAT_R8, DRM_FORMAT_RG88),
> + DRM_MAP(NV12, 2, DRM_FORMAT_R8, DRM_FORMAT_GR88),
> #endif
> DRM_MAP(NV12, 1, DRM_FORMAT_NV12),
> #if defined(VA_FOURCC_P010) && defined(DRM_FORMAT_R16)
This looks very shady. Shouldn't one or the other of these be NV21, with the second plane VU rather than UV?
- Mark
_______________________________________________
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 parent reply other threads:[~2021-12-27 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211210160501.929C341050D@natalya.videolan.org>
2021-12-27 18:56 ` Mark Thompson [this message]
2021-12-28 3:57 ` Chen, Wenbin
2021-12-28 4:38 ` 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=bfb77f48-26eb-69a2-8b1f-d73323ee7315@jkqxz.net \
--to=sw@jkqxz.net \
--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