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: Wed, 14 Nov 2012 16:24:55 +0000	[thread overview]
Message-ID: <bug-56865-502-LZunepbTk8@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-56865-502@http.bugs.freedesktop.org/>


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

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

--- Comment #18 from ka.nick@mail.ru ---
(In reply to comment #17)
> I suspect that it works as intended though it's not what one might expect
> comparing to similar options in proprietary drivers.
I think you're completely right. In my case the issue was provoked by two
things: first, the program I use (GTK driconf o.9.1) suggests MLAA to be set to
8 as default value (however, resets it to 0 by default), and second, that it
did not actually work for me in mesa 8.0. So I was misled a little bit after I
installed mesa 9...

> As far as I understand, expected usage of MLAA with Mesa is to enable it
> only for the applications where you want it (games etc) with either
> app-specific drirc settings or environment variables.
It is probably so. A **huge** problem for me is a common lack of documentation.
I'm okay with English and not too lazy to read but I could hardly find what to
read, though. I mean - relevant while not obsolete. Things usually work in
default configuration, which may not be optimal for some cases, and if I want
to do something about it - this is where troubles begin - for me and maybe for
developers who have to answer my sometimes stupid questions. All this video
stuff looks so complicated and chaotic for me due to lack of documentation... I
even did not comprehend if mesa is commonly responsible only for 3D rendering
how comes erroneously enabled MLAA blurs fonts, too. Fonts currently are
rendered by DDX driver, aren't they?

> So I don't think it's a bug, though perhaps it would be nice to make Mesa
> behave more like other drivers.
Or at least, make things documented somehow. Currently the tuning knobs are
spread across three areas: drirc (which is created somehow, or not, often
beyond the user control); environment variables (hardly documented), Xorg.conf.
Oh yes, there is fourth: USE flags/.configure options. A little bit to
complicated...

Just the same, thank you guys for what you do.

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

[-- Attachment #1.2: Type: text/html, Size: 3021 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-14 16:24 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
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 [this message]
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-LZunepbTk8@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