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.

Wine Devs Have Mixed Feelings Over Direct3D In Gallium3D

Phoronix: Wine Devs Have Mixed Feelings Over Direct3D In Gallium3D

Two days ago we reported on Direct3D being natively implemented in Gallium3D that now allows Direct3D (the 3D portion of the DirectX API) to work on Linux via this advanced graphics driver architecture and unlike Wine's implementation it does not simply translate the calls to OpenGL. This has generated much interest among developers and end-users with there being more than 200 comments in our forums and plenty of discussion elsewhere too. However, some Wine developers seem to be in objection to this work...

I'm a bit disappointed by the reaction of the wine devs on this. Don't know what to make of it. I hope they can work out any issues and will work together with Luca, because it's probably the only chance we have to not make wine suck on the open drivers. So I hope they think about that and, and not only about Nvidia blob and Apple.

Meanwhile, Luca has committed Wine DLLs that use this state tracker so that in fact Wine can now hook into Gallium3D for this Microsoft Direct3D acceleration on the GPU (or on the CPU if using LLVMpipe).

Aside from that I agree with you, you can't ignore that ReactOS had stopped for an audit for a long time due to this: http://marc.info/?l=ros-dev&m=118775346131642&w=2
I'm sure nobody wants that to happen with Wine. Wine is already playing catchup as it is...

I do know about what happened with ReactOS. But I at least get the impression that this implementation was built on the basis of what is a very public and well understood API, unlike the Windows internals. Could Luca comment on whether there was actually any reverse engineering involved?