Re: Christmas list for the kernel

[Denis Vlasenko <vda@ilport.com.ua>]

On Tuesday 22 November 2005 23:41, Jon Smirl wrote:
> On 11/22/05, Kasper Sandberg <lkml@metanurb.dk> wrote:
> > > Currently you have to compile most of this stuff into the kernel.
> > forgive my ignorance, but whats stopping you from doing this now?
> 
> It would be better if all of the legacy drivers could exist on
> initramfs and only be loaded if the actual hardware is present. With
> the current code someone like Redhat has to compile all of the legacy
> support into their distribution kernel. That code will be present even
> on new systems that don't have the hardware.
> 
> An example of this is that the serial driver is hard coded to report
> four legacy serial ports when my system physically only has two. I
> have to change a #define and recompile the kernel to change this.

> The goal should be able to build something like Knoppix without
> Knoppix needing any device probing scripts. Linux is 90% of the way
> there but not 100% yet.
 
It's not such a pressing need IMO. This stuff works, doesn't
need a lot of maintenance, is not too big code size wise, so why
should it be converted ASAP?

As discussed on "PCI core patch" thread, getting specs from
hardware vendors for new stuff is getting harder. When one suddenly
discovers than [s]he cannot run X on shiny new notebook -
_this_ is a serious problem.

> X is also part of the problem. Even if the kernel nicely identifies
> all of the video hardware and input devices, X ignores this info and
> looks for everything again anyway. In a more friendly system X would
> use the info the kernel provides and automatically configure itself
> for the devices present or hotplugged. You could get rid of your
> xorg.cong file in this model.
--
vda
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/