Hi all,

I've just tried r300 out of CVS coupled with the new X.Org packages in
Debian unstable and I am proud to report that everything works!

My hardware is a IBM Thinkpad T42 with:
0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV350
[Mobility Radeon 9600 M10]

I succeeded in playing Quake 3 at a very impressive speed for a driver
that is supposed to kill all my unborn children instead

For the benefit of those who will find this posting on Google, here's
what I did, even though the README is very good at describing what needs
to be done.

1. Check out r300_driver:
cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/r300 co r300_driver
2. Check out Mesa somewhere:
cvs -d :pserver:[EMAIL PROTECTED]:/cvs/mesa co Mesa
3. apt-get source xorg-x11
4. apt-get build-dep xorg-x11
5. cd xc/programs/Xserver/hw/xfree86/drivers/ati, patch -p0 < ati.patch
(If you used Xorg from CVS or a later version, you may not need this step)
6. Remove the build-tree/xc/extras/Mesa directory and replace it with
your checked-out Mesa directory.
7. Go back to the xorg-x11 root and run debian/rules build-arch-only.
Let things happen on their own, while periodically checking to see
whether the Makefiles in xc/programs/Xserver/hw/xfree86/drivers/ati have
been generated. When they have, simply kill the build, navigate to the
directory and issue make, to expedite building. radeon_drv.o is all you
need, and that will exist once the make in the 'ati' dir has completed.
8. Overwrite /usr/X11R6/lib/modules/drivers/radeon_drv.o with the new one.
9. At this point, check your kernel config and disable drm support from
being built in. You will be overriding it with the drm in r300_driver.
If necessary, rebuild and install the kernel. If you are using a stock
kernel this is not necessary as it's already modularized.
10. Here I will quote the README verbatim:

> 4. Create a shadow of the r300/ subdirectory from this source tree in
> the Mesa tree using a command like the following (<Mesa> and
> <r300_driver> must be absolute path names, not relative path names):
>       mkdir <Mesa>/src/mesa/drivers/dri/r300
>       lndir <r300_driver>/r300 <Mesa>/src/mesa/drivers/dri/r300

and

> 6. Make sure your Mesa build uses drm/shared-core/radeon_drm.h from
> this source tree (i.e. set the DRM_SOURCE_PATH environment variable to
> <r300_driver>/drm, cd <r300_driver>/drm ; ln -s shared-core shared
> (because shared is no longer in the CVS tree because it is a left
> over).

where <Mesa> is build-tree/xc/extras/Mesa and <r300_driver> is the path
to your CVS checkout of r300_driver. Do not bother with the
DRM_SOURCE_PATH setting just yet.

11. cd Mesa and edit configs/linux-dri. Reduce DRI_DIRS variable to
include only "dri_client radeon r300" (radeon may not even be necessary)

12. make DRM_SOURCE_PATH=<r300_driver> linux-dri. Remember that
<r300_driver> should be substituted with the path to your CVS checkout
of r300_driver.

13. Copy r300_dri.so and radeon_dri.so into /usr/X11R6/lib/modules/dri.
14. Go back to <r300_driver>/drm/linux-core, and
make LINUXDIR=/path/to/your/kernel/source. If things work out, copy the
resultant kernel modules (*.ko) into your modules tree. If drm and other
dri modules were previously modularized, remember to overwrite the old
ones. Run depmod -ae as root to make sure things are still sane.

At this point, you are done. Purge all fglrx drivers and substitute
fglrx for radeon in your xorg.conf. Set up drm and radeon kernel modules
to load on system bootup. You probably need to reboot to excise the
fglrx kernel module.

Initially, a problem I experienced was that although r300 enabled Direct
Rendering, I hadn't yet removed ATI's hacked up libGL. Once I did, it
all worked.

With any luck, things will work!

And developers, thank you for all your hard work on this driver!

-- 
Joshua Kwan


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to