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)?
[...]
> if there was binary allowed (with any license) maybe dlink themself
> would build a driver, make documentation and provide it on CD, just
Here are too many "maybe"s and "would" in there. Do you have a written
contract or similar stuff?
And who is maintaining that driver and solving all possibly related
problems?
It is not fun to debug software where some unknown piece of code may
have introduced a bug and you can't chase it down since you don't have
the source.
Will $COMPANY have enough capable people to follow LKML and look after
bug reports involving their driver as long as the driver should be
considered maintained?
Will $COMPANY provide versions for not-Intel CPUs where people may put
their hardware into?
The trivial solution is: Don't buy that hardware if you want to run it
on Linux.
Alas, the big difference is: In the Windows world, the hardware
companies are interested to solve problems with their drivers (otherwise
they have no business), in the Linux world they are not.
And that won't change with "officially" allowing binary drivers.
The consequence would be that $COMPANY writes a driver and blames the
rest of the Linux world to change some internal undocumented interface
months lateron just that they can commercially state to "support Linux"
but without any real reason. In the non-evolutionary Windows world this
holds until the next major release, but not on the high-tech front.
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
