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

DRM Change Continues To Cause Debate

Linux Kernel

Published on 29 November 2009 03:03 PM EST
Written by Michael Larabel in Linux Kernel
9 Comments

Kristian Høgsberg on the 6th of November had wrote a message on the DRI development list regarding the libdrm repository. With so much of the Direct Rendering Manager (DRM) work going straight into the Linux kernel -- thanks in large part to all of the work on memory management and kernel mode-setting -- Kristian proposed that the DRM driver code be removed from the separate DRM Git tree. With this message, Kristian created a new DRM repository that dropped all of the linux-core, bsd-core, and shared-core code. Seems simple and straightforward, right? Well, three weeks later with dozens of replies, this change is continuing to cause debate.

After some initial confusion was cleared up, some active DRM developers (such as Jerome Glisse) were in support of this change while others (such as Eric Anholt) thought it would do more harm than good with creating a larger burden on the developers and users wishing to test out this code. Some developers viewed this as a way to get greater testing of it living in the kernel tree that it would get better test coverage with each kernel release candidate and avoiding copying files, while others feared this would force users to upgrade their kernel to obtain simple DRM fixes.

These concerns led Kristian to revise his proposal to pull the latest DRM driver bits from a Linux kernel repository automatically into his libdrm Git repository. Kristian described this work as "[not] an attempt to change how we work, it was merely a re-organisation of the drm.git repo to better reflect and support the de facto workflow." But still, some developers objected.

A week ago, another can of works got opened when one user became disgruntled that the bsd-core code was removed from the tree. While the BSD driver bits were dropped from the tree, so were the Linux bits, but the BSD code was rarely worked on and not even used by the BSD maintainers. As can be seen from this DRM log, the last time the bsd-core was touched inside Mesa/DRM was in March and before that was only worked on every few months almost entirely by a lone FreeBSD developer, Robert Noland. Robert though wasn't even the one complaining about this code location change.

Robert Noland ended up responding to say "the code there is useless and only provided minor historical value." This though didn't settle things and led Vehemens to dispute the number of actual *BSD developers working on the DRM code, code not being shared, and other issues. Here though is a message that describes the FreeBSD DRM situation at least, by Robert himself, but really is just becoming into a public fight between two developers that both actually have the same goal of bettering the *BSD DRM code.

As of today, this mailing list thread remains very active. The changes though already went into effect and the linux/bsd/share-code folders were removed more than a week ago (commit) that reduced the number of lines of code by more than 130,000. Of course, this code remains available, but just not in the master DRM git tree. The linux-core code wasn't worked on in that location in months and the bsd-core code wasn't in even more months.

The DRM BSD code is continuing to be worked on, albeit in a different location and doesn't receive as much love as the Linux DRM. OpenSolaris or FreeBSD/NetBSD/OpenBSD have yet to support the Graphics Execution Manager or TTM for kernel memory management, let alone kernel mode-setting or other recent DRM changes.

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. Scythe Mugen MAX
  2. Intel Core i7 5960X Haswell-E On Linux
  3. Intel 80GB 530 Series M.2 SSD On Linux
  4. With A New Motherboard, The Core i7 5960X Haswell-E Lights Up
Latest Linux Articles
  1. MSAA RadeonSI Gallium3D Performance Preview
  2. Intel Core i7 5960X CPU Core Scaling Under Linux
  3. AMD RadeonSI Gallium3D Performance For 4K Linux Gaming
  4. 9-Way File-System Comparison With A SSD On The Linux 3.17 Kernel
Latest Linux News
  1. Nouveau For Linux 3.18 Gains DP Audio, More Re-Clocking
  2. SUSE Gets Bought Out Again
  3. Enlightenment E19 Officially Released With Its Own Wayland Compositor
  4. OpenMediaVault 1.0 Released As New Linux NAS Alternative
  5. VESA Releases DisplayPort 1.3, Pushes 32.4 Gbits/sec
  6. Opera 25 Beta Has Bookmarks & Linux Support
  7. LLVM Clang Now Builds Even More Debian Packages
  8. Pyston 0.2 Is A Heck Of A Lot Better At Running Python Programs
  9. Linux 3.17-rc5 Kernel Released
  10. FreeBSD 10.1 In Beta Ahead Of Planned Release Next Month
Latest Forum Discussions
  1. New Group Calls For Boycotting Systemd
  2. support for first generation UVD blocks (RV6xx, RS780, RS880 and RV790)
  3. Nvidia joins the ranks of Apple and Microsoft
  4. Hd 6850
  5. nv and xorg.conf under Debian PPC
  6. X.Org Is Looking For Some Female Help
  7. FSF Issues Their Rebuttal To Apple's New iPhone, Watch & Apple Pay
  8. Updated and Optimized Ubuntu Free Graphics Drivers