Bug 27328 - Ability to choose between classic and gallium dri driver
Summary: Ability to choose between classic and gallium dri driver
Status: RESOLVED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: git
Hardware: All All
: medium enhancement
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-26 08:29 UTC by Fabio Pedretti
Modified: 2010-03-27 14:11 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Fabio Pedretti 2010-03-26 08:29:05 UTC
Now that the r300 gallium driver is becoming usable it would be nice to have the ability to choose between the classic and the gallium driver adding an option to the xorg.conf file. This way distributions can provide both drivers with a defined default and let users change to the other if they prefer, rather than having to rename radeong to r300.

Ideally in mesa the r300 driver could be compiled as r300c_dri.so and the gallium driver as r300g_dri.so, and r300_dri.so could be a symlink pointing to the default one (this way the default could be changed inside mesa).

In -ati the default should be r300 (mesa default), leaving the user to force to r300c or r300g.
Comment 1 Michel Dänzer 2010-03-26 10:49:22 UTC
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.
Comment 2 Corbin Simpson 2010-03-27 14:11:18 UTC
Agreed with Michel. The DRI name is picked by the DDX as a known, safe value, and that should not be configurable. Users need to opt in for this. If distros want to provide overriding functionality, they can use a technique like Gentoo's for switching between GLX stacks.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.