Re: [future of drivers?] a proposal for binary drivers.

[Bernd Petrovitsch]

On Tue, 2006-03-14 at 19:50 -0500, Valdis.Kletnieks@xxxxxx wrote:
> On Tue, 14 Mar 2006 00:06:48 +0100, Bernd Petrovitsch said:
> > On Wed, 2006-03-08 at 15:33 +0530, Anshuman Gholap wrote:
> > [...]
> > > into installing it) , he knowing me as a linux person will keep
> > > bugging me, when i tell him to install a kernel source compile it to
> > > allow 16k stack, install ndiswrapper and load the windows driver and
> > 
> > And you seriously think that $COMPANY will rewrite their driver to work
> > with 4K-stacks (which seems to me to be an absolute requirement ATM)?
> 
> From the NVidia drivers changelog:

NVidia is one of the better examples (and I leave the binary driver
discusion out) - they supported their drivers from the start (and the
first years there were lots of trouble with official builds every other
day or so IIRC).

[...]
> Looks like they managed to do that quite some time ago - in fact, before
> some parts of the *in-kernel* code were totally cleaned up....
> 
> So yes, I *do* expect $COMPANY to re-write their driver to support 4K stacks. ;)

Of course implies "maintaing a driver for Linux" that such
maintenance/development/call-it-what-you-want is done (and not only for
4K-stacks - this just a current example and probably needs handling on
the driver side and providing some "compatibility layer" won't work that
good).

My doubt is that (above supposed old-economy) $COMPANY (which was more
or less "forced" to support Linux and didn't "freely" choose that way
like NVidia) writes a driver (or payed someone external once for it) and
considers the "Linux case" closed for the next 3 years (as you would
with a Win*-driver).

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services

-
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/