Re: 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10

From: Greg KH
Date: Sat Mar 12 2005 - 19:04:51 EST


On Sat, Mar 12, 2005 at 11:24:16AM +0100, Stefan Rompf wrote:
> Hi,
>
> Felix von Leitner wrote:
>
> > Did I mention that I'm really tired of you putting stones into ATI's
> > way? You might believe you have a right to piss everyone off, after all
> > people get what they paid for. Or maybe you think you are on a crusade
> > to promote open source software. But if you keep alienating me (I'm a
> > software developer) like this, I spend more time working around this
> > bullshit and less time writing free software. In the end, everyone
> > loses. I sincerely hope some day you people are done pissing in the
> > pool and can create at least some semblance of semi-stable APIs. This
> > house is never going to be safe for living until you stop digging around
> > the foundation.
>
> I cannot agree more. Many developers and maintainers say they don't care about
> binary modules - but I do have the impression a few of them care a lot by
> doing changes in a way that they break the current NVIDIA drivers on every
> new kernel release.

Oh no, our secret is out! :)

> As I read now, it seems to be the same way with ATI. Even GPL drivers
> developed outside the kernel are disfigured over and over with #ifdefs
> on KERNEL_VERSION.

Then get those GPL drivers into the kernel tree, and that will not be
needed at all.

> While I fully understand that no developer wants to support binary modules, I
> would appreciate a little less hostile behaviour. And btw., instable API
> leads to an instable kernel because not everyone can follow the changes.

Please read Documentation/stable_api_nonesense.txt for more info on
exactly _why_ the kernel changes like this.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/