dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 35095] [r300g] HiZ broken in WoW
Date: Sun, 15 May 2011 05:06:36 -0700 (PDT)	[thread overview]
Message-ID: <20110515120637.0452A13004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-35095-502@http.bugs.freedesktop.org/>

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

--- Comment #10 from Chris Rankin <rankincj@googlemail.com> 2011-05-15 05:06:36 PDT ---
(In reply to comment #9)
> Could you test the latest Mesa master branch? There are some new HiZ fixes.

At best, those HiZ fixes didn't help. But I suspect the corrupt area on the
login screen may actually be larger now.

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

  parent reply	other threads:[~2011-05-15 12:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 22:09 [Bug 35095] New: [r300g] More screen corruption in WoW with HyperZ enabled bugzilla-daemon
2011-03-07 22:14 ` [Bug 35095] " bugzilla-daemon
2011-03-07 22:19 ` bugzilla-daemon
2011-03-07 22:23 ` bugzilla-daemon
2011-03-08 21:15 ` bugzilla-daemon
2011-03-08 21:21 ` bugzilla-daemon
2011-03-08 21:25 ` bugzilla-daemon
2011-03-08 22:25 ` bugzilla-daemon
2011-03-08 23:13 ` bugzilla-daemon
2011-03-08 23:17 ` [Bug 35095] [r300g] HiZ broken in WoW bugzilla-daemon
2011-03-08 23:24 ` bugzilla-daemon
2011-05-15  1:40 ` bugzilla-daemon
2011-05-15 12:06 ` bugzilla-daemon [this message]
2011-06-23  7:55 ` bugzilla-daemon
2011-06-25 14:18 ` bugzilla-daemon
2012-12-02  6:13 ` bugzilla-daemon
2012-12-02 12:38 ` bugzilla-daemon
2012-12-02 21:49 ` bugzilla-daemon
2012-12-02 22:00 ` 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=20110515120637.0452A13004F@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).