From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 32296] [r300g] Screen corruption with WoW when HyperZ enabled.
Date: Wed, 26 Jan 2011 15:04:37 -0800 (PST) [thread overview]
Message-ID: <20110126230437.BC0D913004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-32296-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=32296
--- Comment #15 from Chris Rankin <rankincj@googlemail.com> 2011-01-26 15:04:37 PST ---
(In reply to comment #13)
> If you compile with --enable-debug, it should print the hyperz status to
> stderr.
RADEON_HYPERZ=1
RADEON_DEBUG=hyperz
and then I get lots of lines like:
hyper-z features: hiz: 0 @ deadbeef
RV350 has no HiZ, so that's not unexpected. The can_hyperz flag does appear to
be being set as well.
--
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-01-26 23:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 16:06 [Bug 32296] New: [r300g] Screen corruption with WoW when HyperZ enabled bugzilla-daemon
2010-12-24 20:48 ` [Bug 32296] " bugzilla-daemon
2010-12-25 11:26 ` bugzilla-daemon
2011-01-08 23:02 ` bugzilla-daemon
2011-01-08 23:39 ` bugzilla-daemon
2011-01-25 4:59 ` bugzilla-daemon
2011-01-25 8:56 ` bugzilla-daemon
2011-01-25 15:53 ` bugzilla-daemon
2011-01-25 16:14 ` bugzilla-daemon
2011-01-25 16:37 ` bugzilla-daemon
2011-01-25 16:49 ` bugzilla-daemon
2011-01-25 21:32 ` bugzilla-daemon
2011-01-25 21:52 ` bugzilla-daemon
2011-01-25 22:14 ` bugzilla-daemon
2011-01-26 8:35 ` bugzilla-daemon
2011-01-26 23:04 ` bugzilla-daemon [this message]
2011-01-27 21:39 ` bugzilla-daemon
2011-01-27 21:54 ` bugzilla-daemon
2011-01-28 0:09 ` bugzilla-daemon
2011-01-28 0:24 ` bugzilla-daemon
2011-01-28 9:00 ` bugzilla-daemon
2011-01-29 14:47 ` 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=20110126230437.BC0D913004E@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).