Can ReactOS benefit from Gallium3ds support for directX11?

[tgc]

Hi,

As written here Gallium3d (a linux graphics driver framework) now somewhat supports Direct X 10/11. This is not the usual OpenGL wrapper-stuff, but real native DirectX support. Could ReactOS (or the sometimes mentioned ReactX) at some point could benefit from this, or is this too bound to the Linux architecture?

[Z98]

If my memory is still working, we could benefit from anything Mesa did. Gallium on the other hand was tied to something Unixy, whether it was X or something else, which precluded directly using it like we can with Mesa.

[mrugiero]

http://en.wikipedia.org/wiki/Gallium3D

It seems it's platform independent...

BUT, DirectX 10 and 11 support will be close source....

[tgc]

BUT, DirectX 10 and 11 support will be close source....

VMWare wanted it to be close source when they were developing it, but it is now an open source project, and the DirectX 10 and 11 support mentioned in the article is open source.

[Z98]

The issue with Gallium has more to do with the way it interacts with hardware, which happens to be different from how Mesa does it, which is the only way we currently support. Again I may be misremembering or misquoting, but the general gist I got when I spoke with some of the people responsible for 3D stuff was that Gallium wouldn't work, at least not back then. Whether this has changed is very doubtful.

[preston]

in the long term yes. but the code is still experimental and most probably we (or at least I) will wait for Wine's next step in this direction as we already use their dx8/9 implementation and these projects are tied together anyway.

now for the mesa/gallium confusion. right now we are using mesa and its own software rasterizer module (which is kinda fallback when a HW driver lacks some feature or when using a SW driver) and GDI driver to do the actual drawing. what will likely happen sooner or later is using mesa as a state tracker on top of gallium plus the softpipe and gdi winsys driver as a replacement of the current implementation. then we can simply add more state trackers (when they are available) and hw drivers (ditto) to provide support for HW acceleration + other APIs than OpenGL.

[mrugiero]

BUT, DirectX 10 and 11 support will be close source....

VMWare wanted it to be close source when they were developing it, but it is now an open source project, and the DirectX 10 and 11 support mentioned in the article is open source.

Sorry, I think I read from an out to date blog...

[paul]

Well, It is still quite a bit confused in my head.

But Gallium3D was integrated in Mesa main line, in version 7.5 (July 2009).
I THINK that it is still not used much, and that it is optional for now.

And that even if eventually, it would be compilable on Windows and then allows to use the new drivers, for now it is only Linux buildable, instructions being at:
http://www.freedesktop.org/wiki/Softwar ... nceDrivers

OpenVG (accelerated 2D) was added in 7.6.

Mesa 7.8 release notes: "Mesa implements OpenGL ES 1.1 and OpenGL ES 2.0. More informations about OpenGL ES can be found at http://www.khronos.org/opengles/.

OpenGL ES depends on a working EGL implementation. Please refer to Mesa EGL for more information about EGL."

I have no idea what would happens if you try to compile MESA with the options for EGL on Windows as explained on: http://www.mesa3d.org/egl.html (taken from users section on the left pane of http://www.mesa3d.org/ )

[preston]

Well, It is still quite a bit confused in my head.

But Gallium3D was integrated in Mesa main line, in version 7.5 (July 2009).
I THINK that it is still not used much, and that it is optional for now.

And that even if eventually, it would be compilable on Windows and then allows to use the new drivers, for now it is only Linux buildable, instructions being at:
http://www.freedesktop.org/wiki/Softwar ... nceDrivers

OpenVG (accelerated 2D) was added in 7.6.

Mesa 7.8 release notes: "Mesa implements OpenGL ES 1.1 and OpenGL ES 2.0. More informations about OpenGL ES can be found at http://www.khronos.org/opengles/.

OpenGL ES depends on a working EGL implementation. Please refer to Mesa EGL for more information about EGL."

I have no idea what would happens if you try to compile MESA with the options for EGL on Windows as explained on: http://www.mesa3d.org/egl.html (taken from users section on the left pane of http://www.mesa3d.org/ )

Yes you are confused and you are confusing other people now too Gallium and Mesa do share the same repo but that's all. Read my previous post again. Also you can build both mesa and gallium and some of its drivers (trace, softpipe..) on windows just fine.