From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67530] VDPAU state tracker reports wrong codec level
Date: Tue, 30 Jul 2013 12:29:13 +0000 [thread overview]
Message-ID: <bug-67530-502-0MDYI4vmu0@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-67530-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 810 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67530
--- Comment #3 from Christian König <deathsimple@vodafone.de> ---
(In reply to comment #2)
> Good to know! I'll stop bothering the world and his dog about that, then. :-)
> Is this also normal that the decoder only report NV12 and no YV12, UYVY or
> YUYV? Is it some hardware limitation?
Yes that's a hardware limitation, UVD can only decode to an NV12 destination.
Well actually we somewhat abused the query interface here, cause VDPAU asks the
driver what image formats are supported in up/downloads and not as decoding
target.
Should probably fix that at some point as well. On the other hand that should
be really easy to do, so if anybody volunteers...
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1679 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-07-30 12:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 10:37 [Bug 67530] New: Wrong UVD capabilities reported by VDPAU on Brazos bugzilla-daemon
2013-07-30 11:35 ` [Bug 67530] VDPAU state tracker reports wrong codec level bugzilla-daemon
2013-07-30 11:57 ` bugzilla-daemon
2013-07-30 12:29 ` bugzilla-daemon [this message]
2013-08-06 21:19 ` bugzilla-daemon
2013-08-07 10:49 ` bugzilla-daemon
2013-08-13 16:21 ` bugzilla-daemon
2013-08-13 16:31 ` bugzilla-daemon
2013-08-14 11:36 ` 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-67530-502-0MDYI4vmu0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).