On Wed, May 09, 2007 at 09:45:23PM +0200, Gerfried Fuchs wrote: > Though, I'm not too sure if the source is able to properly support the > release kernel - it seems like it's able to support only up to 2.6.16 > kernels, and the new release informations about 0.7.6-4 from upstream > supporting 2.6.17 and 2.6.18 does add to that feeling.
Yes, I think that is the case. There were some unfortunate timing issues here. Having a brand new kernel upload being the last thing to happen before signing off on a release probably isn't exactly a recipe for success in these circumstances. > Could you please upgrade to that new upstream release too? That is the plan here, I hope to do that soon now. > I really wonder why this wasn't possible prior to etch release. :( There were a few regressions, for a few users, in the releases following this one. With 20/20 hindsight, there probably was time to have slipped in one more update of this one that might have been better than the one we have, but each time I assessed that, the release seemed closer than it actually was and I erred on the side of keeping it closer, and of not breaking things for existing users. This code is actively being merged with the mainline kernel now so there is a pretty good chance that any kernel this does not work with, does not need it anyhow. If that stays true, I probably will drop the external module package and only supply the userspace and xorg driver in future releases. Cheers, Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
