From: "Michel Dänzer" <michel@daenzer.net>
To: Robert Hooker <sarvatt@ubuntu.com>
Cc: xorg-devel@lists.x.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH ati] Add Gallium (radeong) support via an xorg.conf option, disabled by default.
Date: Tue, 15 Jun 2010 08:41:25 +0200 [thread overview]
Message-ID: <1276584085.6802.171.camel@thor.local> (raw)
In-Reply-To: <1276561181-11861-1-git-send-email-sarvatt@ubuntu.com>
On Mon, 2010-06-14 at 20:19 -0400, Robert Hooker wrote:
> The r300 gallium driver in mesa is built as radeong_dri.so and the DDX is
> hardcoded to use r300 as the DRI driver name for that generation. this patch
> allows radeong to be used if specified in an xorg.conf with this option:
>
> Option "Gallium" "True"
>
> This only affects DRI2 since the gallium driver requires it, and has the benefit
> of being able to coexist with the classic mesa driver.
>
> Signed-off-by: Robert Hooker <sarvatt@ubuntu.com>
See http://bugs.freedesktop.org/show_bug.cgi?id=27328#c1 :
IMHO xorg.conf would be both overkill and insufficient: the
r300g binary should just be called what it is, namely
r300_dri.so, and then the distro could choose the default via
the installation path / symlinks / whatever, and the user could
override it per application via $LIBGL_DRIVERS_PATH.
--
Earthling Michel Dänzer | http://www.vmware.com
Libre software enthusiast | Debian, X and DRI developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2010-06-15 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 0:19 [PATCH ati] Add Gallium (radeong) support via an xorg.conf option, disabled by default Robert Hooker
2010-06-15 6:41 ` Michel Dänzer [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=1276584085.6802.171.camel@thor.local \
--to=michel@daenzer.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=sarvatt@ubuntu.com \
--cc=xorg-devel@lists.x.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.