r300 driver in extras?

Dave Jones davej at redhat.com
Fri Mar 31 18:58:06 UTC 2006


On Fri, Mar 31, 2006 at 06:32:44PM +0100, David Woodhouse wrote:
 > On Fri, 2006-03-31 at 15:47 +0300, Jonathan Dieter wrote:
 > > It seems that the only difference in Mesa when the r300 is enabled is 
 > > that an extra file (r300_dri.so) is installed in /usr/lib64/dri, and 
 > > that the only difference in the kernel is the drm module is patched to 
 > > not recognize the r300 PCI ids.  It seems that the Mesa problem could be 
 > > easily fixed, but what is the easiest way to fix the kernel (aside from 
 > > providing my own (un)patched kernel)?
 > 
 > We could make the crippling of R300 _optional_, by doing it with the
 > patch below instead of just by ripping the relevant PCI IDs out.
 > 
 > DaveJ?

something got merged yesterday (not yet in the fedora kernel until
I rebase), that changed a lot of this.

============================================
commit f3dd5c37382472a8b245ad791ed768771594e60c
tree 38c9d13de6187f0b67154d7ab643dbaed55280c2
parent 6e5fca53c72c95da92c092411c7ec81e926af632
author Dave Airlie <airlied at linux.ie> Sat, 25 Mar 2006 18:09:46 +1100
committer Dave Airlie <airlied at linux.ie> Sat, 25 Mar 2006 18:09:46 +1100

drm: add new radeon PCI ids..

This adds all the r300 and r400 PCI ids from DRM CVS, it also
makes these cards only initialise when the new xorg driver is
used, as otherwise the DRM can cause lockups.
============================================

relevant bit being..

+       /* if we require new memory map but we don't have it fail */
+       if ((dev_priv->flags & CHIP_NEW_MEMMAP) && !dev_priv->new_memmap)
+       {
+               DRM_ERROR("Cannot initialise DRM on this card\nThis card
+requires a new X.org DDX\n");
+               radeon_do_cleanup_cp(dev);
+               return DRM_ERR(EINVAL);
+       }

I'll drop the cripple-radeon patch today, and we'll see what happens.

		Dave

-- 
http://www.codemonkey.org.uk




More information about the fedora-devel-list mailing list