Removing of GPU drivers from backports
Hi all,
bringing backports to a new version of linux next is a much bigger task now that we have lots of more drivers we backport, especially the GPU driver need a big effort to be backported. My rough estimation is that the GPU driver are taking as much efforts as the wireless drivers and subsystem to be maintained, thereby the wireless driver are supported on much older kernel versions. There is little code shared between the wireless and the GPU drivers expect the build system.
I tried to use the Intel i915 driver on my device with kernel 3.5 and it did not worked (some in kernel errors) and when using kernel 3.7 it also failed (kernel oops).
Who uses the GPU drivers form backports?
Which GPU driver were successfully runtime tested by anyone in the last few months?
As we do not have that big constant man power I am for removing the GPU drivers to make it easier to add support for a new linux next versions. Most of the users are using backports to get a recent wireless driver for their desktop Linux or their (old) Linux on an embedded device.
Hauke
Quoted 4 lines · Hauke Mehrtens
As we do not have that big constant man power I am for removing the GPU drivers to make it easier to add support for a new linux next versions. Most of the users are using backports to get a recent wireless driver for their desktop Linux or their (old) Linux on an embedded device.
For what it's worth, I agree.
I simply don't understand who the target audience is for the GPU/DRM driver backports; unlike the wireless/network drivers, the GPU/DRM subsystem generally requires equally updated userspace in order to take advantage of the newer stuff, and that has its own morass of dependencies.
I don't understand the point of backported regulator drivers either; those tend to be part of the core board support package for a given hardware/SoC design and as such isn't something that's going to be retrofitted into an existing design running an older kernel; and if you're going to be bringing up a new board from scratch, why not use the latest kernel to begin with?
- Solomon
Signature · 3 lines
Solomon Peachy pizza at shaftnet dot org Delray Beach, FL ^^ (email/xmpp) ^^ Quidquid latine dictum sit, altum viditur.
Quoted 6 lines · Solomon Peachy
Quoted 4 lines · Hauke Mehrtens
As we do not have that big constant man power I am for removing the GPU drivers to make it easier to add support for a new linux next versions. Most of the users are using backports to get a recent wireless driver for their desktop Linux or their (old) Linux on an embedded device.
Quoted 7 lines
For what it's worth, I agree.
I simply don't understand who the target audience is for the GPU/DRM driver backports; unlike the wireless/network drivers, the GPU/DRM subsystem generally requires equally updated userspace in order to take advantage of the newer stuff, and that has its own morass of dependencies.
GPU driver addition started from a GSoC project but its main author is busy with other things. As per the talks on backports at LinuxCon I'm fine with removing GPU drivers given we have not found a maintainer for them nor have Linux Distributions stepped up to help with that. I'm happy to remove things unless we get folks starting to take more responsibility over their backports.
We should also only support the latest say, 25 kernels, and stick at that.
That said, patches welcomed to remove ancient kernels then, and Hauke already sent an RFC to remove GPU, that can be respinned as PATCH form and I'll take it.
Quoted 6 lines
I don't understand the point of backported regulator drivers either; those tend to be part of the core board support package for a given hardware/SoC design and as such isn't something that's going to be retrofitted into an existing design running an older kernel; and if you're going to be bringing up a new board from scratch, why not use the latest kernel to begin with?
The idea with that is to provide in-kernel backport support. That opens a new way of supporting backports. I'll be addressing this later in October.
Luis