From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89156] r300g: GL_COMPRESSED_RED_RGTC1 / ATI1N support broken
Date: Tue, 24 Feb 2015 09:13:39 +0000 [thread overview]
Message-ID: <bug-89156-502-jNDyPhNTmx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89156-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 689 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=89156
--- Comment #2 from Stefan Dösinger <stefandoesinger@gmx.at> ---
Created attachment 113786
--> https://bugs.freedesktop.org/attachment.cgi?id=113786&action=edit
Screenshot
ATI1N seems to return random garbage here. Attached is a screenshot from our
3DC tests. The right half is ATI2N, it works OK. The left half is ATI1N, it is
filled with random garbage. The expected result is a solid color on the left
half, with R = 0x7f (plus or minus 1). We're not too particular about the
result of G and B on Windows. On Wine we set G = R and B = R.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1601 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:[~2015-02-24 9:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 16:28 [Bug 89156] r300g: GL_COMPRESSED_RED_RGTC1 / ATI1N support broken bugzilla-daemon
2015-02-21 10:49 ` bugzilla-daemon
2015-02-24 9:13 ` bugzilla-daemon [this message]
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-jNDyPhNTmx@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).