[Mesa-dev] [PATCH v3 0/9] Gallium Nine

Henri Verbeet hverbeet at gmail.com
Fri Nov 14 09:33:45 PST 2014

On 14 November 2014 17:42, Jose Fonseca <jfonseca at vmware.com> wrote:
>> [...] We'd
>> potentially be open to using something closer to the Gallium interface
>> instead of OpenGL on the backend in wined3d. In that scenario wined3d
>> would essentially be the statetracker. The main issue with that
>> approach has always been that the Gallium statetracker/driver
>> interface isn't meant to be stable, and neither is the internal
>> interface between wined3d and e.g. d3d9.
> Yes, I don't recommend gallium for that.
> It sounds you want to design a WINE D3D9 DDI pretty much along the lines of the WDDM D3D9 DDI: http://msdn.microsoft.com/en-us/library/windows/hardware/ff552927(v=vs.85).aspx
> Basically, the runtime is one, but there would be two implementations of that DDI. Runtime would do validation, keep copy of current state for application state queries, etc.
Yeah, essentially. In a way we already have that kind of interface,
but it's wined3d internal instead of a proper API. And of course we'll
want d3d10/11 as well at some point.

More information about the mesa-dev mailing list