dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 32945] New: Lower part of the screen corrupt with HyperZ enabled
Date: Sun,  9 Jan 2011 13:55:27 -0800 (PST)	[thread overview]
Message-ID: <bug-32945-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=32945

           Summary: Lower part of the screen corrupt with HyperZ enabled
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: sa@whiz.se


Created an attachment (id=41815)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=41815)
Screenshot of gears

When HyperZ is used on my RV570 the lower part of the screen isn't rendered
correctly.  I'm attaching a screenshot of glxgears, but it's also visible in
most real-world games and apps.

I'm not sure if this is the same as bug 29851 since the hardware differs.

(HyperZ gives a pretty nice performance boost otherwise, about a 30% fps
increase with Doom 3 in 1680x1050!) 

System environment:
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- GPU: RV570
-- Model: Asus EAX1950Pro 256MB
-- Display connector: DVI
-- xf86-video-ati: 6.13.2
-- xserver: 1.9.2
-- mesa: ac6306e9ca904ae9674bf2a15222efe4cb861bf5
-- drm: 2.4.23
-- kernel: 2.6.37

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-01-09 21:55 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-09 21:55 bugzilla-daemon [this message]
2011-01-09 23:07 ` [Bug 32945] Lower part of the screen corrupt with HyperZ enabled bugzilla-daemon
2011-01-10 16:00 ` bugzilla-daemon
2011-01-25  5:00 ` bugzilla-daemon
2011-01-25 14:32 ` bugzilla-daemon
2011-01-25 14:34 ` bugzilla-daemon
2011-01-25 15:54 ` bugzilla-daemon
2011-01-25 16:06 ` bugzilla-daemon
2011-01-25 16:33 ` bugzilla-daemon
2011-01-25 22:29 ` bugzilla-daemon
2011-01-25 22:55 ` bugzilla-daemon
2011-01-25 23:37 ` bugzilla-daemon
2011-01-26  0:38 ` bugzilla-daemon
2011-01-26 15:59 ` bugzilla-daemon
2011-01-28  0:10 ` bugzilla-daemon
2011-01-28 11:08 ` bugzilla-daemon
2011-01-28 12:38 ` bugzilla-daemon
2011-02-11  2:10 ` [Bug 32945] [r300g] HyperZ: Wrong size in the HiZ clear packet causes the zbuffer not to be fully cleared bugzilla-daemon
2011-03-01  0:34 ` bugzilla-daemon
2011-03-01 12:05 ` bugzilla-daemon
2011-03-01 12:06 ` bugzilla-daemon
2011-03-03 20:52 ` bugzilla-daemon
2011-03-06 22:07 ` bugzilla-daemon
2011-03-06 22:12 ` bugzilla-daemon
2011-03-07 20:01 ` [Bug 32945] [RADEON:KMS:R300G] " bugzilla-daemon
2011-03-07 20:41 ` [Bug 32945] [RADEON:KMS:R300G] HiZ: Weird behavior with 3 pipes bugzilla-daemon
2011-03-10 21:13 ` bugzilla-daemon
2011-03-11  3:40 ` bugzilla-daemon
2011-03-11 16:47 ` bugzilla-daemon
2011-03-11 19:33 ` 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=bug-32945-502@http.bugs.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