[ubuntu-x] Status of kernel X drivers
Christopher James Halse Rogers
raof at ubuntu.com
Thu Feb 18 22:30:07 UTC 2010
On Thu, 2010-02-18 at 10:29 -0800, Bryce Harrington wrote:
> On Thu, Feb 18, 2010 at 02:57:18PM +0200, Timo Aaltonen wrote:
> > On Thu, 18 Feb 2010, Christopher James Halse Rogers wrote:
> > > I'd suggest that we stick with our current libdrm < 2.4.18, lbm-nouveau,
> > > and xserver-xorg-video-nouveau stack, and cherry pick & backport
> > > whatever fixes we want to grab. In which case, as long as there's a
> > > 2.6.33 drm in lbm, the nouveau stack is happy.
> > 2.4.18 has other fixes in it, so better to just revert the offending
> > commit with a patch, and then decide if the ABI bump is worth it. Less
> > work than pulling a number of patches on top of 2.4.17.
> I'd agree. Plus it'll be easier to explain "we're carrying 2.4.18 minus
> patch foo".
> Which is the commit(s) that needs reverted?
libdrm would need b496c63143e9a4ca02011582329bce2df99d9b7c and I think
also 88e8a8bbaf026aa10225880001ab7ca1c392168a reverted.
If we're comfortable with pulling from the nouveau kernel tree for
linux-backports-modules-nouveau, then going over the API bump would
indeed make cherry-picking and backporting fixes easier. The API bump
hasn't made it out of that tree yet, as far as I'm aware.
If we're additionally going to have lbm packages for intel and radeon
built from 2.6.34, I think it makes sense to pull from the nouveau tree
now, and later switch to the .34 tree when we pull the rest of the drm
drivers for lbm.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 490 bytes
Desc: This is a digitally signed message part
More information about the kernel-team