On Thu, 2007-08-02 at 20:05 -0400, Mike Frysinger wrote: > > sounds good to me ... so to tie back to the source of the thread, crappy > closed source vendor drivers are not a valid reason to hold up stabilization > of a kernel
Who ever said they were crappy? Maybe the documentation on usage is
crappy, but drivers have consistently gotten much better. These days
pretty solid IMHO for my uses.
They just did not compile against 2.6.22 due to some files being moved
around or etc. I happen to like the drivers, and they are the only thing
I can use to get DRI from my hardware.
Last I checked there was a version of ati-drivers available for stable
systems. So by stabilizing 2.6.22 you will effectively break those
systems. Not breakage in portage's eyes, but people upgrading their
systems won't be able to run the latest stable kernel with the latest
stable ati-drivers.
FYI, the patches in bug #183480 [1] allow one to use the most current
ati-drivers with a 2.6.22 kernel. As I am now while I am composing this
message. Having applied said patches and bumped ebuild locally. Just
needs to happen in tree :)
1. http://bugs.gentoo.org/show_bug.cgi?id=183480
--
William L. Thomson Jr.
Gentoo/Java
signature.asc
Description: This is a digitally signed message part
