On Sun, Feb 21, 2010 at 2:49 PM, Andrew Benton <b3n...@gmail.com> wrote: > On 21/02/10 20:57, Agathoklis D. Hatzimanikas wrote: >> I don't think this can be done for the current LFS release that will ship >> with 2.6.32. The Book already says that the latest available 2.6.32.x >> should be used. The backported patch, it might be applied to 2.6.32.8 >> but probably it won't apply to the next minor releases of 2.6.32. >> >> I think this ticket should wait for the next LFS release that will >> update to 2.6.33 and then a BLFS ticket is justified. >> >> Generally speaking, I disagree to backport such huge stuff in the kernel, >> unless it's for a security issue. But the 2.6.32 is already a long term >> supported kernel, which means in my mind, no new features added but only >> bug fixes, so this job is already done by the kernel team. >> > > I agree. Although Nouveau is in 2.6.33 it's still in the staging area, it's > not in the > kernel proper. I like Nouveau, I started using it on some of our computers a > couple of > months ago. It allows me to use some Nvidia cards that wouldn't work with the > nv driver. > Google earth works really well. > If someone wants to use Nouveau they should just use a 2.6.33 kernel. It > shouldn't be > too hard for someone who's done LFS
More importantly, fedora is able to backport nouveau and other drm features because they have the drm maintainer, Dave Airlie, to make things work. They also employ one of the nouveau developers, Ben Skeggs, to make nouveau work. LFS has nobody like this and shouldn't pretend to be able to support it. LFS should only include work like this when upstream blesses it and puts it into stable releases. I know the radeon developers weren't happy when distros started enabling the experimental kms features and they got flooded with bug reports about things breaking. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
