So once again it came to gallium vs non-gallium battle... I kinda don't have much more to say about it that I haven't already said before - we do not intend to work on Gallium because it does not seems the best way to write 3d driver to us. And I honestly don't think there is any advantage of throwing away the i965 driver that works, just for the sake of rewriting it from scratch with gallium backend.
However - all the code is open, all the documentation on how the hardware works is already available up to the Ivy Bridge generation GPUs, so nothing prevents someone from simple writing a i965g driver again. Please, feel free to do so - this is all open-source!
Well, to be honest, the idea behind Gallium is to create 1 general codebase that everyone shares, so I don't think anyone would argue too much that it is a superior way of writing a driver, compared to writing one from scratch entirely for your own hardware.
The point of Gallium is to reduce labor for hardware that lacks the resources that Intel can put out.
From that point of view, it is unfortunate that Intel's work doesn't benefit other hardware as much as it could. As someone using the r600g driver, that directly includes myself.
However, from an Intel POV the most important thing is your own driver, and I can understand that even if I don't particularly like it.
Though if you did have Gallium support, you'd already have support for certain things (like OpenCL, among others) that your driver currently doesn't have. So it's not entirely a 1-way street.
Last edited by smitty3268; 07-06-2012 at 01:19 AM.
The problem here is of course Microsoft. Windows does not yet support PowerPC. The Linux desktop market is of course too small to invest in special hardware for it.
About hardware being closed, I don't care about that if my hardware works with open-source software. And Intel hardware does that.