Doesn't the r300g driver already do that ?
I wouldn't hesitate to go with an AMD card at the moment. Up until 2 months ago, I was running a Radeon 4770 on the open source drivers without any issues. I upgraded to a Radeon 6850 last month, and for work reasons I need to use the Catalyst drivers (paid OpenCL development). As soon as Clover is capable of doing what I need it to do, I'll switch back to r600g+clover.
For desktop usage and lightweight 3D, there's nothing wrong with the OSS radeon drivers. If you need GL 3/4 features, you might need to use the Catalyst drivers. Both sets of drivers have been quite stable for me in Ubuntu 11.04 and Windows 7 x64.
Because that would be a worthless comparison. We already know that Mesa3D is slow and pretty much absolutely useless for anything other than being a reference-test renderer. Comparing the speed of anything to that would be like comparing the land speed of a vehicle to that of an office building.
Showing the speed of LLVMPipe on its own is useful. We can see that it hits playable framerates in some cases. Putting the hardware results in there helps give you an idea of just how fast LLVMPipe is, e.g. that it's comparable in speed to a low-end hardware renderer (well, with the FOSS drivers, at least). That's actually meaningful. That tells you that LLVMPipe is serious stuff. You now both have solid numbers telling you if LLVMPipe is fast enough for your needs and you have a meaningful reference point for just how fast it is compared to buying an extra piece of GPU hardware.
IMHO, if you have an i5 with 4 cores and more than 3GHz per core, you are not likely to have a slower GPU than what you can achieve using LLVMpipe. Neither are you using (almost sure) a bad supported GPU, like an Unichrome. I'm not even sure if a VIA chipset from that ages can support an i5 processor.
So, the comparison made in the benchmark is still useless.
It works perfectly here. Did you report a bug?Originally Posted by phoronix