From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 24047] s3tc broken on r600
Date: Tue, 1 Jun 2010 02:59:35 -0700 (PDT) [thread overview]
Message-ID: <20100601095935.D343C1300DF@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-24047-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=24047
--- Comment #11 from Andy Furniss <lists@andyfurniss.entadsl.com> 2010-06-01 02:59:35 PDT ---
(In reply to comment #10)
> ping
s3tc has never worked for me using a RV670 with git drivers, it affects all the
games I've tried - etqw, quake4 demo, et wolf, ut2004 demo and doom3 demo.
Of course disabling s3tc in .driconf will workaround it apart from quake 4
(refuses to start without s3tc) and etqw (which then hits some other shader
errors).
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2010-06-01 9:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-24047-502@http.bugs.freedesktop.org/>
2010-01-04 10:53 ` [Bug 24047] s3tc broken on r600 bugzilla-daemon
2010-04-17 17:39 ` bugzilla-daemon
2010-04-17 18:26 ` bugzilla-daemon
2010-04-18 16:58 ` bugzilla-daemon
2010-05-27 0:02 ` bugzilla-daemon
2010-06-01 2:51 ` bugzilla-daemon
2010-06-01 9:59 ` bugzilla-daemon [this message]
2010-06-01 10:15 ` bugzilla-daemon
2010-06-02 17:45 ` bugzilla-daemon
2010-07-12 20:25 ` bugzilla-daemon
2010-07-23 12:58 ` bugzilla-daemon
2010-07-23 14:32 ` bugzilla-daemon
2010-07-23 17:07 ` bugzilla-daemon
2010-07-23 17:25 ` bugzilla-daemon
2011-07-31 10:44 ` bugzilla-daemon
2011-11-29 2:18 ` bugzilla-daemon
2011-11-29 3:29 ` bugzilla-daemon
2011-11-29 9:47 ` bugzilla-daemon
2011-11-29 9:49 ` bugzilla-daemon
2011-11-29 10:19 ` bugzilla-daemon
2011-11-29 15:04 ` bugzilla-daemon
2011-11-30 1:01 ` 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=20100601095935.D343C1300DF@annarchy.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.