From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109783] YUV422 support not advertised for VAProfileJPEGBaseline decoding
Date: Mon, 25 Feb 2019 22:57:10 +0000 [thread overview]
Message-ID: <bug-109783-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1379 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109783
Bug ID: 109783
Summary: YUV422 support not advertised for
VAProfileJPEGBaseline decoding
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: andrescj@chromium.org
QA Contact: dri-devel@lists.freedesktop.org
Hi. I'm trying to detect the VAAPI JPEG decoder capabilities using
vaQueryConfigAttributes(). I'm getting VA_RT_FORMAT_YUV420 as the only value
for VAConfigAttribRTFormat when the profile is VAProfileJPEGBaseline and the
entrypoint is VAEntrypointVLD. However, based on [1], it seems that the JPEG
decoder would be happy to decode YUV422 images (in fact, YUV422 decoding works
when I call vaCreateSurfaces() with VA_RT_FORMAT_YUV422).
Note that when I use vaQuerySurfaceAttributes(), I only get NV12 for
VASurfaceAttribPixelFormat, so YUV422 is also not advertised there.
Is this intended behavior?
[1]
https://gitlab.freedesktop.org/mesa/mesa/blob/master/src/gallium/state_trackers/va/picture.c#L607-610
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2863 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-02-25 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 22:57 bugzilla-daemon [this message]
2019-02-28 3:23 ` [Bug 109783] YUV422 support not advertised for VAProfileJPEGBaseline decoding bugzilla-daemon
2019-09-25 18:49 ` bugzilla-daemon
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=bug-109783-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.