From: Linus Torvalds <firstname.lastname@example.org>
Subject: Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
Date: Mon, 12 Jan 2004 03:26:54 GMT
On Sat, 10 Jan 2004, Thomas Winischhofer wrote:
> The whole framebuffer stuff in 2.6 is ancient. (Look at the file dates.)
Note that the fb stuff is ancient because it's basically not maintained as
far as I'm concerned.
I occasionally get huge drops from James, and they invariably break stuff.
Which means that I often decide (espcially when trying to stabilize
things) that I just can't _afford_ to apply the fr*gging patches. Because
by past experience applying one of the big "everything changes" patches
tends to break more things that it fixes.
I'm sorry, but this i show it is. The fbcon people have been changing
interfaces faster than they have been fixing bugs in the code. Together
with the fact that most of the development seems to happen in outside
trees, and nobody ever sends me fixes relative to the released tree, this
makes for a pretty bad situation.
I really think that development should happen in the regular tree, or at
least be synched up in reasonable chunks THAT DO NOT BREAK everything.
I realize that some fb developers seem to disagree with me, but the fact
is, the way things are done now, fb will _always_ be broken. Most people
for whom the standard kernel works will never test the fb development
trees, so those trees will never get any amount of reasonable testing. As
a result, they WILL be buggy, and synching with them WILL be painful as
There is a d*mn good reason for why development should happen
incrementally, and in the standard trees, and not in some outside tree.
For one: testing. For another: figuring out when things break in a timely