From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 26735] r600: rendering artifacts
Date: Tue, 06 Nov 2012 10:27:39 +0000 [thread overview]
Message-ID: <bug-26735-502-5EjOHFxtQN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-26735-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 793 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=26735
Török Edwin <edwin+mesa@etorok.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #13 from Török Edwin <edwin+mesa@etorok.net> ---
(In reply to comment #12)
> Note: classic r600 driver has been abandoned.
> Please use r600g (gallium driver) instead.
>
> Is this still an issue with a newer driver/kernel?
Rendering looks correct now, tested with r600g version '3.0 Mesa 9.1-devel
(git-e87a578)' (R600_LLVM=0).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2330 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2012-11-06 10:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 21:04 [Bug 26735] New: r600: rendering artifacts bugzilla-daemon
2010-02-24 21:04 ` [Bug 26735] " bugzilla-daemon
2010-02-24 21:04 ` bugzilla-daemon
2010-02-24 21:05 ` bugzilla-daemon
2010-02-24 21:05 ` bugzilla-daemon
2010-02-24 21:05 ` bugzilla-daemon
2010-02-24 21:05 ` bugzilla-daemon
2010-02-24 21:05 ` bugzilla-daemon
2010-02-24 21:10 ` bugzilla-daemon
2010-02-24 21:21 ` bugzilla-daemon
2010-02-24 21:57 ` bugzilla-daemon
2010-02-25 9:17 ` bugzilla-daemon
2012-11-02 16:26 ` bugzilla-daemon
2012-11-06 10:27 ` bugzilla-daemon [this message]
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-26735-502-5EjOHFxtQN@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;
as well as URLs for NNTP newsgroup(s).