Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
d3d9_gallium_state_tracker [2014/05/29 03:26]
okias [Roadmap]
d3d9_gallium_state_tracker [2014/06/02 18:17] (current)
okias
Line 1: Line 1:
-====== Gallium D3D9 state tracker know also as gallium-nine or "d3d9 st". ====== +Moved to [[d3d9]].
- +
- +
-Consist from two parts +
-  * Mesa libd3dadapter library +
-  * Wine dlls (d3d9.dll.so, gdi32.dll.so, user32.dll.so, wineps.drv.so and winex11.drv.so) +
- +
-At this moment, must be compiled both mesa and wine from special repos or has to be patched. +
-Correct way it's build mesa and wine from git repositories, placed here +
-  * https://github.com/chrisbmr/Mesa-3D (gallium-nine branch) +
-  * https://github.com/chrisbmr/wine (d3dadapter9-wip branch) +
- +
-You should build mesa as usual, only change is passing <code>--enable-nine</code>+
-For wine build, only thing you'll need is already builded mesa with enabled nine. +
- +
-When you got this working, run <code>regedit</code> +
-go to +
-<code>HKCU->Software->Wine->Direct3D</code> and create DWORD named UseNative. Set value to 1 for enable, 0 to disable. +
- +
-As first thing, you may want try run __wine/dlls/d3d9/tests__ and see what pass. +
- +
-==== Roadmap ==== +
- +
-  * (1) Pass the tests (dlls/d3d9/tests) +
-  * (2) have an idea how to handle later d3d10 and d3d11 +
-  * (3) Show clear evidence that performance of d3d9 can't be achieved through translation d3d9 -> opengl. +
-  * (4) Handle applications that do opengl and d3d on the same window. +
-  * (5) Have an interface between wine and mesa that allows independent updates of mesa and wine +
- +
- +
-Also check other wiki pages as: +
-  * [[d3d9_upstream|Review for upstream inclusion]] +
-  * [[d3d9_debugging|Debugging]] +
-  * [[d3d9_supported_hardware|Tested Hardware]] +
-  * [[d3d9_demos|Demos]]+