From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64143] New: vdpau (shaders) regression since vl/buffer: use 2D_ARRAY instead of 3D textures
Date: Thu, 02 May 2013 09:08:51 +0000 [thread overview]
Message-ID: <bug-64143-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1129 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=64143
Priority: medium
Bug ID: 64143
Assignee: dri-devel@lists.freedesktop.org
Summary: vdpau (shaders) regression since vl/buffer: use
2D_ARRAY instead of 3D textures
Severity: normal
Classification: Unclassified
OS: All
Reporter: adf.lists@gmail.com
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
non uvd mpeg2 decode was never perfect on my rv790 (though I think that is a
software issue as it's the same with xvmc softpipe - vdpau softpipe untested
due to crash).
It is, however a lot worse for vdpau since -
commit 7d2f2a0c890b1993532a45c8c392c28950ddc06e
Author: Christian König <christian.koenig@amd.com>
Date: Tue Apr 30 14:40:40 2013 +0200
vl/buffer: use 2D_ARRAY instead of 3D textures
Signed-off-by: Christian König <christian.koenig@amd.com>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2640 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 reply other threads:[~2013-05-02 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 9:08 bugzilla-daemon [this message]
2013-05-02 14:08 ` [Bug 64143] vdpau (shaders) regression since vl/buffer: use 2D_ARRAY instead of 3D textures bugzilla-daemon
2013-05-02 20:14 ` bugzilla-daemon
2013-05-03 9:44 ` bugzilla-daemon
2013-05-03 10:33 ` 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-64143-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.