From: Keith W. <ke...@tu...> - 2003-07-31 15:49:13
|
Ian Romanick wrote: > Michel D=C3=A4nzer wrote: >=20 >> On Wed, 2003-07-30 at 03:06, Ian Romanick wrote: >> >>> Antoine REVERSAT wrote: >>> >>> >>>> I just compiled dri from the CVS for my radeon 9000 Mobbility card=20 >>>> (r250 lf) and it wont work as good as it is expected to (I.E : 30=20 >>>> fps in Quake3) The thing is when i do a glxinfo it is reported as a=20 >>>> r200 chip which it isn't... So i'd like to know if you are aware of=20 >>>> this and what solutions do i have. I also wanted to know if support=20 >>>> should be better or if this is normal. >>>> For information i'm running Gentoo linux 1.4_RC4 with 2.4.21-ac3=20 >>>> patched kernel (patched for the mmu_cr4 problem) I'm running Xfree=20 >>>> 4.3.0. >>>> If you need more informations let me know. >>> >>> >>> Here's a patch that should clear some of that up, at least for the=20 >>> R200-family of chips. I did change the code to include=20 >>> xf86PciInfo.h. In spite of the comment there, it doesn't seem to=20 >>> produce any errors. Is this a safe change to make? Also, do we=20 >>> really need to check the device ID against R100-family IDs in the=20 >>> R200 driver? >> >> >> Apparently, people do try to use the wrong drivers on the Mesa embedde= d >> and whatnot branches... >=20 >=20 > How can that be? The user has to select which 3D driver to use (i.e.,=20 > the 2D driver doesn't select it for them)? What's to stop someone with= =20 > an R200 from "selecting" the MGA driver? There's no 2D driver. It would be simple to add some checking to ensure the chipid is recognize= d by=20 the 3d driver, just hasn't been done yet. Keith |