Linked by Thom Holwerda on Thu 5th Feb 2009 13:33 UTC, submitted by Colin Finck
Thread beginning with comment 347312
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
I believe what you propose is http://linux.insigma.com.cn/en/">already with the Linux Unified Kernel project. That has some exciting potential. With Wine hooking into ReactOS's API instead, we stand to see a lot of performance benefits.
The Linux kernel guys have already stated that they would not be opposed to adding Win32 kernel calls into the Linux kernel. They've added calls from other kernels, and Linux itself is a reimplementation of an older proprietary standard (same as ReactOS, only further along), so it kinda makes sense. Linux kernel devs are a pragmatic bunch after all.
Given the Linux kernel developers strong objection to -Linux- binary drivers, I don't see it ever happening. At least not in the main-line tree.
- Gilboa






Member since:
2005-07-07
Wine actually has to actually implement every D3D and wrap that to an equivalent (enough) OpenGL call. For the harder stuff, they even have to implement shader compilers, and translators to go from D3D shaders to OpenGL shaders. Even worse, they have to re-implement the hacks and workarounds on a per game basis that nVidia and ATI have built into their proprietary drivers - never mind all the application specific hacks that may be in Windows itself.
Much of these problems would be solved in ReactOS by simply using the bits of code that come with the hardware drivers - and some of them even by running MS proprietary libraries (though that probably violates licenses, so I'm sure they will attempt to rewrite a lot of that anyway - like Direct X).
What I'd like to see, is a collaboration between the React OS guys, the Wine guys, and the Linux guys, so that we can get some of the windows code (like binary D3D driver support) into the Linux Kernel (modularize that part of the ReactOS kernel, add some glue code so it loads in Linux kernel, and we're off), so that Wine could simply take advantage of what has already been implemented in the windows binary drivers and ReactOS (well, they are still a ways off, but still).
The Linux kernel guys have already stated that they would not be opposed to adding Win32 kernel calls into the Linux kernel. They've added calls from other kernels, and Linux itself is a reimplementation of an older proprietary standard (same as ReactOS, only further along), so it kinda makes sense. Linux kernel devs are a pragmatic bunch after all.