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 Articles & Reviews
  1. Khronos Group Announces Vulkan, OpenCL 2.1, SPIR-V
  2. Samsung 850 EVO SSD Linux Benchmarks
  3. Kubuntu 15.04 Is Turning Out Quite Nice, Good Way To Try Out The Latest KDE
  4. 5-Way Linux Distribution Comparison On The Core i3 NUC
  5. OCZ ARC 100 Linux SSD Benchmarks
  6. Lenovo ThinkPad X1 Carbon Works Great As A Linux Ultrabook
Latest Linux News
  1. Samba 4.2 Brings Transparent File Compression & Clustering Support
  2. Mutter 3.15.91 Fixes Wayland Nested Compositor Mode, Pointer Constraining
  3. NVIDIA Opens Up CPU-Based PhysX Code
  4. SPIR-V In GCC Is Already Being Talked About
  5. Valve Launches SteamOS Sale, Confirms A Lot Of New Linux Games
  6. Ubuntu Cloud Switches Over To Using Systemd By Default
  7. Xfce 4.12 Might Make It For Fedora 22
  8. Pictures Of The Near Production Ready Ubuntu Tablet
  9. OpenVG Support Stripped From Gallium3D
  10. Mozilla Is Getting Excited About WebGL 2
Most Viewed News This Week
  1. The Tremendous Features Of Fedora 22
  2. Confirmed: Vulkan Is The Next-Gen Graphics API
  3. Xfce 4.12 Released After Nearly Three Years Of Work
  4. 8cc: A Small C11 Compiler
  5. LLVM 3.6 & Clang 3.6 Deliver More Features, Complete C++14 Support
  6. Unreal Engine Made Free By Epic Games
  7. ALSA 1.0.29 Released
  8. Canonical's Latest Demo Of Ubuntu Unity 8 Convergence In Action