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 11:35:58 +0000 [thread overview]
Message-ID: <bug-67530-502-aSn8NFsvoW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-67530-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 747 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67530
Christian König <deathsimple@vodafone.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
Summary|Wrong UVD capabilities |VDPAU state tracker reports
|reported by VDPAU on Brazos |wrong codec level
--- Comment #1 from Christian König <deathsimple@vodafone.de> ---
Indeed, so far we have hardcoded the level in vlVdpDecoderQueryCapabilities.
Should be updated to correctly return the supported codec level.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2186 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 11:35 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 ` bugzilla-daemon [this message]
2013-07-30 11:57 ` [Bug 67530] VDPAU state tracker reports wrong codec level bugzilla-daemon
2013-07-30 12:29 ` bugzilla-daemon
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-aSn8NFsvoW@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).