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 48747] regression [bisected]: display corruption in google earth/glxgears using git r600g on RS780M
Date: Tue, 17 Apr 2012 07:16:39 +0000	[thread overview]
Message-ID: <bug-48747-502-wMNBPsuHUY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-48747-502@http.bugs.freedesktop.org/>

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

--- Comment #7 from Michel Dänzer <michel@daenzer.net> 2012-04-17 00:16:39 PDT ---
(In reply to comment #6)
> I am sorry I can't patch my kernel since I use a precompiled one.

It's not hard to build your own Debian kernel with a patch. It'll be a skill
very useful to you for testing bug fixes.


(In reply to comment #5)
> Yes, it works without problems with xf86-video-ati driver from git.

Even with Option "ColorTiling2D"?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2012-04-17  7:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16  2:02 [Bug 48747] New: regression [bisected]: display corruption in google earth/glxgears using git r600g on RS780M bugzilla-daemon
2012-04-16  2:40 ` [Bug 48747] " bugzilla-daemon
2012-04-16 10:23 ` bugzilla-daemon
2012-04-16 14:11 ` bugzilla-daemon
2012-04-16 14:27 ` bugzilla-daemon
2012-04-17  2:41 ` bugzilla-daemon
2012-04-17  4:36 ` bugzilla-daemon
2012-04-17  7:16 ` bugzilla-daemon [this message]
2012-04-17 11:42 ` bugzilla-daemon
2012-05-16 16:59 ` bugzilla-daemon
2012-05-17  4:48 ` 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-48747-502-wMNBPsuHUY@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