Re: Linux drivers management

[Martin Mares]

Hello!

> And then think, why do you need to _build_ drivers in the first place.
> Wouldn't it be better to have one vmware.ko which insmod's with all
> 2.6 versions , from 2.6.0 to 2.6.16-rc2 , and throw "upgrade pain"
> away completely ? 

Well, you want the vmware.ko to contain machine code for at least 17
different architecture the kernel runs on? ;-)

> If kernel has stable ABI, basic/default driver is included on
> installation CD, and all you need to do 
[...]

... and I'm screwed if I happen to use a 2 years old network card with
written for a 2.4.x kernel, while I am running on 2.6.x.

> is to launch ./install-linux.sh from CD in your shell or click OK and
> enter your root password in GUI box. Newer/better driver - just go to
> device manufacturer's website, download installation package and
> install this driver. Without rebuilding. 

While now, I don't need to install or rebuild anything, just use the
stock kernel which already contains the drivers :)

> And what to do if you've bought new hardware, installed it and _voila_
> - NO IN-TREE DRIVER exists ?

The same like what I do if I buy new hardware and no Linux driver exist
-- call myself an uninformed ignoramus, because that's who I am.

> Please, don't force your preferences over others'

Doesn't this sentence apply to you as well? ;-)

				Have a nice fortnight
-- 
Martin `MJ' Mares   <mj@xxxxxx>   http://atrey.karlin.mff.cuni.cz/~mj/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
It said, "Insert disk #3," but only two will fit!
-
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/