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 56865] Mesa 9.0 extremely slow and produces fading output on radeon Evergreen
Date: Thu, 08 Nov 2012 17:11:39 +0000	[thread overview]
Message-ID: <bug-56865-502-iQfosBGdEp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-56865-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 947 bytes --]

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

--- Comment #10 from Alex Deucher <agd5f@yahoo.com> ---
(In reply to comment #8)
> Just to make sure we understood each other correctly...
> MLAA worked for me in 8.0 and it seems to be a regression in 9.0.
> Is there something I can do about it?

I'm saying I don't think MLAA was actually enabled in 8.x due the changes in
the way drirc options are handled in gallium drivers between 8.x and 9.x.  The
changes you see in 9.x are a result of MLAA being enabled when you switched
whereas it was previously not enabled under 8.x.  Here is the relevant commit:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=e7c177ec9e37d0c406c3b0ef8f228159d7ee5d69
Prior to that commit, the driver name in your drirc had to be "dri" to work
with gallim drivers.  After that commit, it now matches the actual driver name,
e.g., "r600".

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1979 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

  parent reply	other threads:[~2012-11-08 17:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08 11:23 [Bug 56865] New: Mesa 9.0 extremely slow and produces fading output on radeon Evergreen bugzilla-daemon
2012-11-08 11:50 ` [Bug 56865] " bugzilla-daemon
2012-11-08 11:51 ` bugzilla-daemon
2012-11-08 12:04 ` bugzilla-daemon
2012-11-08 16:36 ` bugzilla-daemon
2012-11-08 16:37 ` bugzilla-daemon
2012-11-08 16:39 ` bugzilla-daemon
2012-11-08 16:40 ` bugzilla-daemon
2012-11-08 16:41 ` bugzilla-daemon
2012-11-08 16:45 ` bugzilla-daemon
2012-11-08 16:58 ` bugzilla-daemon
2012-11-08 17:04 ` bugzilla-daemon
2012-11-08 17:11 ` bugzilla-daemon [this message]
2012-11-08 17:31 ` bugzilla-daemon
2012-11-08 17:45 ` bugzilla-daemon
2012-11-08 17:49 ` bugzilla-daemon
2012-11-08 17:50 ` bugzilla-daemon
2012-11-08 18:54 ` bugzilla-daemon
2012-11-08 19:17 ` bugzilla-daemon
2012-11-08 19:38 ` bugzilla-daemon
2012-11-11  8:51 ` bugzilla-daemon
2012-11-14 16:24 ` bugzilla-daemon
2012-11-14 16:31 ` bugzilla-daemon
2019-09-18 19:01 ` 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-56865-502-iQfosBGdEp@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