Roland Scheidegger wrote:
Since people have asked for it, I decided I'd give it a try...
So here it is, a unified radeon driver (no not r300, only r100 and r200).
http://homepage.hispeed.ch/rscheidegger/dri_experimental/ati_radeon.tar.bz2
exectuable generated will be called radeon_dri.so, for
Am Samstag, den 19.02.2005, 01:11 +0100 schrieb Nicolai Haehnle:
Hi,
On Saturday 19 February 2005 00:46, Roland Scheidegger wrote:
There is some problem with driconf, it seems to have some problems
because the driver's name (radeon) does not match what it expects
(r200). Likewise, I
Since people have asked for it, I decided I'd give it a try...
So here it is, a unified radeon driver (no not r300, only r100 and r200).
http://homepage.hispeed.ch/rscheidegger/dri_experimental/ati_radeon.tar.bz2
exectuable generated will be called radeon_dri.so, for r200 you can just
use a
This is good for mesa-solo. It removes the need to sort out r100 vs
r200. Now if the radeon module loads you know you need the radeon
driver.
--
Jon Smirl
[EMAIL PROTECTED]
---
SF email is sponsored by - The IT Product Guide
Read honest
Hi,
On Saturday 19 February 2005 00:46, Roland Scheidegger wrote:
There is some problem with driconf, it seems to have some problems
because the driver's name (radeon) does not match what it expects
(r200). Likewise, I couldn't figure out how you'd have 2 separate config
sections for both
On Sat, 19 Feb 2005, Nicolai Haehnle wrote:
Hi,
On Saturday 19 February 2005 00:46, Roland Scheidegger wrote:
There is some problem with driconf, it seems to have some problems
because the driver's name (radeon) does not match what it expects
(r200). Likewise, I couldn't figure out how you'd have
