Mailinglist Archive: opensuse (3605 mails)

< Previous Next >
Re: [SLE] Re: And another 10.1 showstopper
  • From: Rajko M <rmatov101@xxxxxxxxxxx>
  • Date: Thu, 01 Jun 2006 01:38:32 -0500
  • Message-id: <447E8B68.8090703@xxxxxxxxxxx>
Darryl Gregorash wrote:

<snip>

What's next on the chopping list of proprietary modules? ATI and nVidia?
Bye-bye ndiswrapper, perhaps? I know I won't be holding my breath
waiting for BluRay support to show up in the Linux kernel. If we are
going to be forced to use only hardware that is on some Linus-approved
list, I do hope that Linus will spend a reasonable amount of time to
make sure the list is a) kept current, and b) made widely available.
Otherwise, we might as well pack it in, and run out to buy XP.


Darryl,

why in the world one would like to put in the kernel foreign code.
There is option to put binary drivers in user space. That will prevent kernel crashes due to bad written drivers. That is how any modern OS deals with device drivers (including XP).

It is not GPL license question (you should read that too), as some vendors want you to believe, it is just technical.

If driver is not at kernel level and buggy it will not run like any other bad written software, but your system will.

If driver is bad and part of the kernel than it will crash whole system (are you old enough to remember BSOD times). To make use of such driver someone has to debug it. Do you think that any of hardware vendors will ever try to ask MS to debug device drivers without giving technical specs and source code?

If driver is bad and binary only how to debug that?
Kernel developers accepting to debug device drivers where source code is open, but not additional load of guesswork to debug binaries, not to mention that such binaries come with legal load that only lawyers can decipher.

The only thing that happens by trowing binary drivers out of kernel is that responsibility for writing and debugging drivers is back to vendors. Scream that they have no resources for that might be real, but than it is up to them to open the code or technical data and let people help them.

--
Regards,
Rajko.

--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx


< Previous Next >
References