If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Gallium drivers are a work in progress. The comparisons that you linked to do not include any of the performance improvements that are the subject of this thread, nor do they include Page Flipping which will not be available until Linux kernel 2.6.38 is released.
Not 100% sure about this, but I think Phoronix test suite sets vblank_mode to 0 and pageflipping is only used with vblank_mode=1, so there wouldn't probably be any visible change.
Exactly. From a Linux perspective, proprietary drivers have only one real advantage -- they can share development effort with proprietary drivers for other OSes and in that way benefit from a much larger development effort.
Pageflipping as it is currently implemented in dri2 only flips during the vblank period (swap interval of 1) so it's limited to the refresh rate. Ideally, we also support pageflipping when the swap interval was 0 as well so you'd get atomic pageflipping (with tearing) for maximum frame rates. dri2 needs to work to enable this however. Even with vblank synchronized pageflipping, it still helps performance in that is reduces memory bandwidth requirements and pipeline latency since you don't have to do an additional blit to copy the back buffer to the front buffer.
Tell that to the "blobs must die, only open source drivers should be allowed in Linux" bozos.
There's not blobs must die only open source drivers should be allowed in linux bozos. What there are is an operating system controls your computer and takes responsibility for controlling your computer. You shouldn't have 3rd parties in there doing things you don't fully understand. You'll reverse enegineer a good deal of what they are doing just by working with them. But they are still an unknown ingredient in your sauce. And they cause testing problems because if something in their package causes a problem in your package then you have to search around in the dark for an answer and then wait for them to fix it.
I know redhat is very hardcore about security and I'm sure working with some of these companies gives you a whole lot of conciousness that you are working with pedo bear and want to start screaming stranger danger for some odd reason. All you have to do is watch things like the fence sync. They always operate the same way. Create a crisis and then solve it quickly not giving everyone enough time to figure out everything that is going on and why it's going on. They are addicted to creating crisis because they already know how they want it solved and they want it solved with everybody throwing thier hands up in disgust.