All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 32296] New: [r300g] Screen corruption with WoW when HyperZ enabled.
Date: Fri, 10 Dec 2010 08:06:09 -0800 (PST)	[thread overview]
Message-ID: <bug-32296-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: [r300g] Screen corruption with WoW when HyperZ
                    enabled.
           Product: Mesa
           Version: git
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: rankincj@googlemail.com


Created an attachment (id=40990)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=40990)
Screen corruption with HyperZ enabled.

I have upgraded to the 2.6.36.2 Linux kernel, and tried to enable HyperZ for
World of Warcraft using RADEON_HYPERZ=1. Upon entering the game, the bottom
part of the screen is corrupt. (See attachment.)

This happens with both my RV350 and my M66. The blank area starts of correctly
textured, but quickly becomes a blank area in a single colour.

-- 
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:[~2010-12-10 16:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-10 16:06 bugzilla-daemon [this message]
2010-12-24 20:48 ` [Bug 32296] [r300g] Screen corruption with WoW when HyperZ enabled 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
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=bug-32296-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.