From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 37724] r300g with HyperZ/Z compression: occlusion queries are messed up in ut2004 (regression, bisected)
Date: Fri, 10 Jun 2011 00:47:52 -0700 (PDT) [thread overview]
Message-ID: <20110610074753.3E4B013004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-37724-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=37724
--- Comment #9 from Fabio Pedretti <fabio.ped@libero.it> 2011-06-10 00:47:52 PDT ---
(In reply to comment #8)
> (In reply to comment #6)
> > > I don't consider Hyper-Z ready yet but thanks for testing it.
> >
> > It is enabled by default now, is it by accident?
> Perhaps you mean that it always reports this?
> r300: AA compression RAM: YES, Z compression RAM: YES, HiZ RAM: NO
>
> It used to mean that those features are enabled, but now it means that those
> are available in HW. Now if hyperz is enabled, these are printed:
> radeon: Acquired Hyper-Z.
> radeon: Released Hyper-Z.
Yes, I see this:
r300: DRM version: 2.8.0, Name: ATI RV530, ID: 0x71c5, GB: 1, Z: 2
r300: GART size: 509 MB, VRAM size: 256 MB
r300: AA compression RAM: YES, Z compression RAM: YES, HiZ RAM: YES
I didn't noticed the
radeon: Acquired Hyper-Z.
radeon: Released Hyper-Z.
that indeed get printed when RADEON_HYPERZ=1 is set, however I also noticed
that with openarena I get the same FPS with or without it.
--
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-06-10 7:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 17:17 [Bug 37724] New: occlusion queries are messed up in ut2004 (regression, bisected) bugzilla-daemon
2011-05-29 17:57 ` [Bug 37724] " bugzilla-daemon
2011-05-29 19:41 ` bugzilla-daemon
2011-05-30 11:03 ` bugzilla-daemon
2011-05-30 18:31 ` bugzilla-daemon
2011-05-30 20:59 ` [Bug 37724] r300g with HyperZ/Z compression: " bugzilla-daemon
2011-06-09 11:37 ` bugzilla-daemon
2011-06-09 14:21 ` bugzilla-daemon
2011-06-09 14:59 ` bugzilla-daemon
2011-06-10 7:47 ` bugzilla-daemon [this message]
2012-01-05 16:03 ` bugzilla-daemon
2012-01-05 22:04 ` bugzilla-daemon
2012-01-05 23:14 ` bugzilla-daemon
2012-01-05 23:54 ` bugzilla-daemon
2012-01-06 0:18 ` bugzilla-daemon
2012-12-02 6:11 ` bugzilla-daemon
2017-02-06 23:23 ` bugzilla-daemon
2017-02-07 6:43 ` bugzilla-daemon
2017-02-26 16:55 ` bugzilla-daemon
2017-02-27 13:05 ` bugzilla-daemon
2017-02-27 19:57 ` bugzilla-daemon
2017-03-11 8:43 ` bugzilla-daemon
2017-03-11 8:44 ` 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=20110610074753.3E4B013004F@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