1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

Gallium3D's Direct3D 10/11 State Tracker To Be Nuked

Mesa

Published on 11 March 2013 12:36 PM EDT
Written by Michael Larabel in Mesa
21 Comments

The Direct3D state tracker for Gallium3D that for a short time provided hope of a native Direct3D implementation for Linux of the Microsoft Direct3D 10/11 APIs without simply being a translator layer to OpenGL, is set to be nuked from mainline Mesa.

The Direct3D Gallium3D implementation was published back in 2010 and provided hope of support for the Microsoft graphics API on Linux. It worked to some extent and could even be hooked into Wine. Among Wine developers though, there were mixed feelings about the D3D state tracker since it was rather Linux-specific and bound to using the Mesa Gallium3D hardware drivers. There's also legal uncertainty concerning this state tracker for implementing the Microsoft API.

In the past two and a half years, the Direct3D state tracker fell into bit-rot and was disabled by default from building last year. Without any real users of the state tracker, Mesa developers aren't really motivated to support its continued existence.

This morning Jose Fonseca of VMware proposed a patch to eliminate the D3D1X code outright.

This trims over 27,000 lines of code from Mesa for this state tracker that's no longer really being used. Of course, it can be obtained from Git and earlier Mesa releases should anyone want to revive the Direct3D on Linux support.

Gallium3D's Direct3D 10/11 State Tracker To Be Nuked
The Direct3D state tracker is set to go the way of Chernobyl... From the Phoronix tour of Chernobyl in 2010.

Christoph Bumiller of Nouveau did write a follow-up message to the Monday morning patch about earlier capabilities of this D3D1X state tracker.
This one *did* kind of work, notably also with wine, but it still has loads of bugs and I just don't have the time to improve it; and then add those missing bits like deferred contexts, virtual functions, compute shader or UAV support. Also gallium's still not completely able to support everything properly. It did acquire some of the missing parts though since last time I touched it.

I had succeeded in making Unigine Heaven run (taking a little shortcut with sm4 to nv50, extending the gallium interface for features like tessellation that are still years ahead for all the other parties would not have been well received at that time, at least I had that impression), but all the more complex games I tested crashed somewhere and I wasn't going to try to debug binary blobs (most of them seemed to require those missing features, too).

Anyway, just meant to say, it *could* have been useful had someone finished it ... if only with wine. So I'm fine with removing it since I don't expect anyone to get back to it. Trying to decide between "farewell" and "good riddance" for all the pain its bugs caused me.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux Hardware Reviews
  1. 13-Way Low-End GPU Comparison With AMD's AM1 Athlon
  2. ASUS AM1I-A: A Mini-ITX Board For Socketed Kabini APUs
  3. Mini-Box M350: A Simple, Affordable Mini-ITX Case
  4. Overclocking The AMD AM1 Athlon & Sempron APUs
Latest Linux Articles
  1. How Much Video RAM Is Needed For Catalyst R3 Graphics?
  2. Ubuntu 12.04 LTS vs. 14.04 LTS Cloud Benchmarks
  3. Ubuntu 12.04.4 vs. 13.10 vs. 14.04 LTS Desktop Benchmarks
  4. AMD OpenCL Performance With AM1 Kabini APUs
Latest Linux News
  1. OpenELEC 4.0 Beta 6 Works On 4K Graphics, RPi ALSA
  2. Linux 3.15 Lands Some DRM Graphics Driver Fixes
  3. AMD Is Disabling DPM Support For RV770 GPUs
  4. ReactOS Working On A Community Windows OS
  5. Borderlands Is Being Considered For Linux
  6. Mesa 10.0 & 10.1 Stable Get Updated
  7. Getting Hit By The Variable Performance Of The Public Cloud
  8. Git 2.0 Test Releases Begin With Many Changes
  9. Wine 1.7.17 Works On Its Task Scheduler, C Run-Time
  10. The Improv ARM Board Still Isn't Shipping; Riding A Dead Horse?
  11. Debian To Maintain 6.0 Squeeze As An LTS Release
  12. Wasteland 2 Is Finally Released For Linux Gamers
Latest Forum Discussions
  1. The GNOME Foundation Is Running Short On Money
  2. Updated and Optimized Ubuntu Free Graphics Drivers
  3. Catalyst 14.3 Beta
  4. Suggestions about how to make a Radeon HD 7790 work decently?
  5. Radeon 8000M problematic on Linux?
  6. Linux Kernel Developers Fed Up With Ridiculous Bugs In Systemd
  7. After Jack Keane, RuseSoft will briing Ankh 3 to Linux through Desura
  8. Suspected PHP Proxy Issue