From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89156] r300g: GL_COMPRESSED_RED_RGTC1 / ATI1N support broken
Date: Sun, 15 Feb 2015 16:28:56 +0000 [thread overview]
Message-ID: <bug-89156-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 869 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=89156
Bug ID: 89156
Summary: r300g: GL_COMPRESSED_RED_RGTC1 / ATI1N support broken
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
Assignee: dri-devel@lists.freedesktop.org
Reporter: stefandoesinger@gmx.at
QA Contact: dri-devel@lists.freedesktop.org
r300g on r500 chips advertises GL_ARB_texture_compression_rgtc, but the
red-only format GL_COMPRESSED_RED_RGTC1 (aka ATI1N in ATI / d3d9 speak) is
broken. This breaks the d3d8 and d3d9 visual tests in Wine. It can also be seen
by running the rgtc-teximage-01 test in piglit.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2174 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:[~2015-02-15 16:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 16:28 bugzilla-daemon [this message]
2015-02-21 10:49 ` [Bug 89156] r300g: GL_COMPRESSED_RED_RGTC1 / ATI1N support broken bugzilla-daemon
2015-02-24 9:13 ` bugzilla-daemon
2015-02-24 21:38 ` bugzilla-daemon
2015-02-26 9:36 ` bugzilla-daemon
2015-02-26 11:23 ` bugzilla-daemon
2015-02-26 11:46 ` bugzilla-daemon
2015-02-26 13:26 ` bugzilla-daemon
2015-03-02 13:34 ` bugzilla-daemon
2015-03-02 13:50 ` bugzilla-daemon
2015-03-02 14:12 ` bugzilla-daemon
2015-03-09 20:05 ` 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-89156-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.