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 (r250 lf) and it wont work as good as it is expected to (I.E : 30 fps in Quake3) The thing is when i do a glxinfo it is reported as a r200 chip which it isn't... So i'd like to know if you are aware of this and what solutions do i have. I also wanted to know if support should be better or if this is normal. For information i'm running Gentoo linux 1.4_RC4 with 2.4.21-ac3 patched kernel (patched for the mmu_cr4 problem) I'm running Xfree 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 R200-family of chips. I did change the code to include xf86PciInfo.h. In spite of the comment there, it doesn't seem to produce any errors. Is this a safe change to make? Also, do we really need to check the device ID against R100-family IDs in the R200 driver?
Apparently, people do try to use the wrong drivers on the Mesa embedded and whatnot branches...
How can that be? The user has to select which 3D driver to use (i.e., the 2D driver doesn't select it for them)? What's to stop someone with an R200 from "selecting" the MGA driver?
Is this change really needed or even useful? I suspect this will only serve to produce more 'my chip isn't properly detected!' reports when it doesn't make any difference for the driver operation.
It's certainly not "needed," but *I* think it's useful. :) Dunno...
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
