From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 32296] [r300g] Screen corruption with WoW when HyperZ enabled.
Date: Wed, 26 Jan 2011 15:04:37 -0800 (PST)
Message-ID: <20110126230437.BC0D913004E@annarchy.freedesktop.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from annarchy.freedesktop.org (annarchy.freedesktop.org
[131.252.210.176])
by gabe.freedesktop.org (Postfix) with ESMTP id B4FB39E73D
for ;
Wed, 26 Jan 2011 15:04:37 -0800 (PST)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=32296
--- Comment #15 from Chris Rankin 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.