Its the same situation in GL apps (which I did mention, I only used glxgears as the prime example cause it should be heeps faster considering it doesn't do texturing).
In general I agree. However, it does usefully suggest that Chris isn't getting hardware acceleration. He needs to find out why his install isn't working rather than worry about tweaking optimizations.
well, DRI is enabled, so apart from the possability of DRI's mesa hitting sw paths I dunno what else to hunt for.
I'm really not sure about this, but I believe there could be a severe performance problem when using pci radeons (at least on x86). I haven't seen any measurements of this, and few people seem to have such hardware.
But by using the "BusType" option, I've forced pci mode on my radeon 9000pro agp, and the results are simply terrible. In theory, results should probably be pretty much the same as AGP 1x (same raw data rata, as it's operating as a pci 66mhz device afaik), but it's very different in practice. (Tests on other OS certainly show there is next to zero performance difference for graphic cards of this generation and fillrate-heavy games such as Q3A between AGP and PCI). However, since this isn't a "true" pci card, the chipset (or the driver?) might not like this mode of operation (not sure what could be a problem, but you never know - maybe someone with more knowledge of the drm/gart stuff could answer that).
Results (AXP 1600, 9000pro, 1GB sdram, KT133A Chipset):
glxgears QuakeIII (1024x768, graphic options all set to high)
AGP 4x 1910 62.5
AGP 1x 1860 61.1
PCI 200 16.8Roland
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
