From a Mesa perspective, Gallium3D is just a new HW driver layer at the lowest level of the Mesa code, alongside all the existing HW driver abstractions. You still need Mesa if you want to run OpenGL applications. Mesa is roughly a million lines of code; Gallium3D won't be replacing all of that.
We plan to stick with the old Mesa HW driver model until we have basic 3D functionality going for our latest GPUs (for the simple reason that developers know it and just finished bringing up the same functionality on 5xx parts), then to jump across to the Gallium3D-based code paths for all subsequent development. We think that will get functionality into our users hands most quickly -- and most of the code we write will be directly useable in the Gallium3D drivers.
We plan to stick with the old Mesa HW driver model until we have basic 3D functionality going for our latest GPUs (for the simple reason that developers know it and just finished bringing up the same functionality on 5xx parts), then to jump across to the Gallium3D-based code paths for all subsequent development. We think that will get functionality into our users hands most quickly -- and most of the code we write will be directly useable in the Gallium3D drivers.
Comment