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

The Fight Over Merging Drivers Back Into X Server

X.Org

Published on 16 September 2011 02:39 AM EDT
Written by Michael Larabel in X.Org
26 Comments

The debate that started back up again this week at XDC2011 Chicago about merging drivers back into the X.Org Server has now moved online. Jesse Barnes has published the pros / cons that were mentioned at the X.Org Developers' Conference this week to the X.Org development mailing list for developers to now debate the idea online. This has been a hotly disputed matter for the past two years.

Jesse Barnes, who is in support of merging the video and input drivers back into the X.Org Server, wrote the following message to xorg-devel with the pros and cons.
At XDC this week we discussed merging drivers back into the server tree. One thing I found frustrating about the discussion was that we didn't have a whiteboard nor a list of the pros & cons of such a change. So I'd like to capture that here (from memory) to let us continue the discussion about whether it's worth it or not.

Luc, I think you're the most vocal opponent of this move, so I've cc'd you so you can enumerate any issues I've forgotten.

Anyway, as I recall, the issues are as follows:

Pros:
1) easier to propagate API changes across drivers (just like Linux)
1a) thus easier to change ABI 2) developers focused on driver development now have more incentive to make sure the server works well so regular releases can still happen (i.e. more people working on blockers whether driver or not as releases approach) 3) allows removal of driver compat code for various server versions
3a) thus removes combinations of driver+server that developers have to support & test 4) increased test coverage for the server as users wanting current driver code will be building new servers too

Cons:
1) more work for distros to backport just driver changes to old servers (especially if people follow through on (3) above)
1a) if backporting is harder, new hardware support will be more difficult to land in "enterprise" level distros
2) harder for users to just upgrade drivers independently, now they'll have to build the whole server
2a) thus less testing of current driver code from technical users

I've already made my views pretty clear; I'd prefer merging the drivers back in. But I don't do as much work on the DIX or DDX as I used to, and lots of others would be affected as well, so I'd like to hear what people think. Have I captured the pros & cons fully? What to distro maintainers think? And driver developers, both input & output?

Thanks,
Jesse

Michel Dänzer, who is now at AMD but was not at XDC2011, was quick to respond saying that out-of-tree drivers would become second class citizens. He brings up that out-of-tree drivers would just not be the binary blobs (i.e. NVIDIA and AMD proprietary drivers), but also the Gallium3D Xorg state tracker. Michel also says, "Speaking as a radeon driver developer, merging the driver into the server tree would be unworkable at this point because since the "new development model" has been in effect, it's not possible to get even trivial changes into the server tree without a ridiculous amount of time/effort."

Alex Deucher also expressed he doesn't see much advantage in moving the X.Org drivers back into the server.

Plus there's several other email comments from developers, both those that were in attendance at XDC2011 and not. Continue the heated discussion thread here. (I just landed in Munich and will have more time to go through the read later.)

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. AMD Radeon R9 290: Gallium3D vs. Catalyst Drivers
  2. AMD Radeon R9 290 Open-Source Driver Works, But Has A Ways To Go
  3. Trying The Configurable 45 Watt TDP With AMD's A10-7800 / A6-7400K
  4. Sumo's Omni Gets Reloaded
Latest Linux Articles
  1. Testing For The Latest Linux Kernel Power Regression
  2. The Most Energy Efficient Radeon GPU For AMD Linux Gaming
  3. 20-Way Radeon Comparison With Open-Source Graphics For Steam On Linux Gaming
  4. Preview: OS X 10.10 Yosemite vs. Ubuntu Linux GPU Performance
Latest Linux News
  1. Enlightenment E19 RC3 Shows Off The New Wayland Compositor
  2. Metro Redux Is Going To Require OpenGL 4.x On Linux
  3. Jailhouse v0.1 Released As A Basic Hypervisor For Linux
  4. Google's Chromebook "Samus" Now Supported By Coreboot
  5. Chrome 38 Now In Beta With Exciting Advancements
  6. Ubuntu's Utopic Unicorn 14.10 Beta 1 Released
  7. Genode OS 14.08 Has New GUI Architecture, Pluggable VFS
  8. Another Intel Linux Power Regression Is Being Investigated
  9. DNF Makes It A Step Closer To Replacing Yum On Fedora
  10. OS Battle: Linux Takes 1.7% Desktop Marketshare
Latest Forum Discussions
  1. Canonical Joined The Khronos Group To Help Mir/Wayland Drivers
  2. Users defect to Linux as OpenBSD removes Lynx from base system
  3. Radeon HD5670 and Ubuntu 14.04
  4. Updated and Optimized Ubuntu Free Graphics Drivers
  5. AMD Releases UVD Video Decode Support For R600 GPUs
  6. Best Radeon for a Power Mac G5?
  7. OC capability - Intel Core i5 4690K & Biostar Hi-Fi Z97WE
  8. Announcing radeontop, a tool for viewing the GPU usage