From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 32888] [r600g] GL_EXT_texture_compression_s3tc support
Date: Thu, 17 Feb 2011 00:06:55 -0800 (PST) [thread overview]
Message-ID: <20110217080655.67AC0130009@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-32888-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=32888
--- Comment #6 from Tobias Jakobi <liquid.acid@gmx.net> 2011-02-17 00:06:55 PST ---
Retested with the latest d-r-t and at at least on my RV740 the new CS checker
code seems to do the job right.
@Dave: Would it be safe now to also advertise the remaining two BC formats in
r600g? The BC4 and BC5 one? Also, is it intended that the s3tc_to_blittable
(and the reset function) take a level parameter, which isn't used inside the
function?
Concerning FEAR: I don't think this is related to texture compression. I
fiddled around with the ingame performance options yesterday and the GPU resets
disappeared when I switched the engine from DX9 level to DX8 level pixel
shaders. Maybe this is related to the GLSL piglit tests that still lockup the
GPU.
Anyway, apart from manually enabling the envvar, this issue looks fixed to me.
--
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:[~2011-02-17 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 2:22 [Bug 32888] New: [r600g] GL_EXT_texture_compression_s3tc support bugzilla-daemon
2011-02-01 21:57 ` [Bug 32888] " bugzilla-daemon
2011-02-06 15:50 ` bugzilla-daemon
2011-02-06 16:14 ` bugzilla-daemon
2011-02-09 10:39 ` bugzilla-daemon
2011-02-15 10:08 ` bugzilla-daemon
2011-02-17 8:06 ` bugzilla-daemon [this message]
2011-02-17 8:22 ` bugzilla-daemon
2011-02-17 12:10 ` bugzilla-daemon
2011-08-19 5:21 ` 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=20110217080655.67AC0130009@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 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).