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 32639] [RADEON::R300C] artifacts on dinoshade, neverball and other GL softwares
Date: Sat, 19 Mar 2011 15:03:59 -0700 (PDT)	[thread overview]
Message-ID: <20110319220359.50AB913000C@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-32639-502@http.bugs.freedesktop.org/>

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

--- Comment #7 from Alex Deucher <agd5f@yahoo.com> 2011-03-19 15:03:59 PDT ---
(In reply to comment #6)
> I've google a little bit.
> The r300g is the gallium driver for r300?
> 
> The problem is that gallium actually is too slow. On my notebook, is much
> faster the swrast driver, but if I disable gallium, I get the artifacts.
> 
> At this time, on this kind of hardware (I've a Radeon X1200), gallium is almost
> unusable.

enable llvm in your mesa build:
--enable-gallium-llvm

-- 
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-03-19 22:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-24 15:01 [Bug 32639] New: Artifacts on dinoshade, neverball and other softwares bugzilla-daemon
2010-12-24 15:02 ` [Bug 32639] " bugzilla-daemon
2010-12-24 15:03 ` bugzilla-daemon
2010-12-24 15:04 ` bugzilla-daemon
2011-03-07 19:23 ` [Bug 32639] [RADEON::R300C] artifacts on dinoshade, neverball and other GL softwares bugzilla-daemon
2011-03-19 21:49 ` bugzilla-daemon
2011-03-19 21:54 ` bugzilla-daemon
2011-03-19 22:03 ` bugzilla-daemon [this message]
2011-03-20  1:13 ` bugzilla-daemon
2011-03-21  8:39 ` bugzilla-daemon
2011-03-21  8:43 ` bugzilla-daemon
2011-10-15 18:14 ` 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=20110319220359.50AB913000C@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).