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

What Parts Of X.Org Should Be Killed With Fire?

X.Org

Published on 17 September 2010 03:49 AM EDT
Written by Michael Larabel in X.Org
20 Comments

Originally at the X.Org Developers' Summit here in Toulouse this week there was going to be a talk entitled "Kill It With Fire" where Corbin Simpson (mostly known for his work on the ATI R300 Gallium3D driver) was going to be speaking about what drivers or parts of X.Org should be eliminated from the stack. This talk though is no longer occurring, in part as Corbin is no longer in attendance; he washed his US passport in the laundry.

Corbin has wrote a summary of what he was going to talk about on the X.Org Wiki. One of the items that has been talked about recently has been XAA vs. EXA and whether to eliminate the prior since EXA/UXA is superior to that of the ancient XFree86 Acceleration Architecture. However, XAA will not be killed off anytime soon since there still are old drivers (the niche ones outside of Intel/Nouveau/Radeon) and hardware that aren't a good fit for EXA. In particular, there's the older hardware that doesn't work well for heavily variable-stride allocations, compositing with alpha, and using 3D engines. As a result, XAA or EXA will not be killed off anytime soon. Even if EXA support was stripped away from the DDX drivers, it still can be accelerated on GPUs via the 3D engine with shaders by the X.Org state tracker in Gallium3D that implements EXA and X-Video.

Living within Mesa are a few obscure drivers that could die with little or few people noticing, like the Mach64, MGA, TdFX, and Savage DRI drivers, but since they at least receive build system fixes (but really no further development), Corbin sees no reason to let them die.

Corbin would like to see the R300 and R600 classic DRI drivers stripped from Mesa though as soon as the R300g and R600g drivers are mature. The ATI R300g (Gallium3D) driver is pretty much mature and is on-par with the classic driver but many in better cases, faster in some OpenGL tests, and more feature-rich thanks to the growing number of Gallium3D state trackers. The R300g and R300 Mesa drivers support up through the ATI Radeon X1000 series. The R600g driver is still not yet on-par with the R600 classic driver or comparable to the R300g driver, but it's quickly advancing and soon should be there with support through the ATI Radeon HD 5000 "Evergreen" hardware.

Legacy code from Mesa should also be stripped as soon as possible (such as GLSL parsing code that's no longer used by Intel's new GL Shading Language compiler). On the opposite end, Corbin wants to pull in Mesa / Gallium3D patches for adding in Haiku, AROS, and Syllable support patches.

On the kernel side of the Linux graphics stack, there are many frame-buffer drivers that this student developer would like removed, but first they need to be ported over to KMS. However, there's not a lot of hardware for these obscure drivers in use and these FB drivers vary already in code quality state. Much activity on this side isn't expected in the near future.

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 Articles & Reviews
  1. NVIDIA's Latest Maxwell Line-Up Against AMD With Catalyst On Linux
  2. Preliminary Tests Of Intel Sandy Bridge & Ivy Bridge vs. Broadwell
  3. AMD FX-8320E Performance On Linux
  4. Linux Compiler Benchmarks Of LLVM Clang 3.5 vs. LLVM Clang 3.6-rc1
  5. Intel Broadwell HD Graphics 5500: Windows 8.1 vs. Linux
  6. Linux Benchmarks Of NVIDIA's Early 2015 GeForce Line-Up
Latest Linux News
  1. Intel Broadwell-U P-State vs. ACPI CPUFreq Scaling Linux Performance
  2. DragonFlyBSD Is Almost To Linux 3.10 Era Intel Graphics Support
  3. New Beta Of Witcher 2 Aims For Greater Performance
  4. NVIDIA Tegra DRM Driver Supports Atomic Mode-Setting In Linux 3.20
  5. Linux "GHOST" Vulnerability Hits Glibc Systems
  6. Linux Game Publishing Remains Offline, Three Years After The CEO Shakeup
  7. PlayStation 4 System Compiler Support Landing In LLVM
  8. Now-Closed KDE Vulnerabilities Remind Us X11 Screen Locks / Screensavers Are Insecure
  9. Vivaldi: A New Chromium-Powered, Multi-Platform Browser
  10. KDE Plasma 5.2 Officially Released
Most Viewed News This Week
  1. Windows 10 To Be A Free Upgrade: What Linux Users Need To Know
  2. LibreOffice 4.4 Is Coming Soon With New Features
  3. TraceFS: The Newest Linux File-System
  4. My Initial Intel Broadwell Linux Experience With The ThinkPad X1 Carbon
  5. Broadwell Linux Ultrabook Running MUCH Cooler Than Haswell
  6. Interstellar Marines On Linux With Catalyst: Bull S*#@
  7. Linux Users Upset By Chromium's Busted HiDPI Support
  8. LZHAM 1.0 Lossless Data Compression Codec Released