From: Adrian Bunk <bunk@stusta.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: abonilla@linuxwireless.org, "'Andreas Steinmetz'" <ast@domdv.de>,
"'Arjan van de Ven'" <arjan@infradead.org>,
"'Denis Vlasenko'" <vda@ilport.com.ua>,
"'linux-kernel'" <linux-kernel@vger.kernel.org>
Subject: Re: Wireless support
Date: Tue, 9 Aug 2005 01:29:57 +0200 [thread overview]
Message-ID: <20050808232957.GR4006@stusta.de> (raw)
In-Reply-To: <1123528018.15269.44.camel@mindpipe>
On Mon, Aug 08, 2005 at 03:06:58PM -0400, Lee Revell wrote:
> On Mon, 2005-08-08 at 12:56 -0600, Alejandro Bonilla wrote:
> > Again, the point is that ndiswrapper is a great project, but people
> > uses it for the leftovers! We *shouldn't* buy leftovers or from Manuf
> > that don't care about Linux.
>
> If you are always speccing out new systems then of course, but in the
> real world I have some customers who need to dual boot and ideally it
> would work on their existing hardware. Linux is a harder sell if people
> need to replace a lot of their gear.
That's the advantage of such drivers.
I see at least two disadvantages:
First, it doesn't encourage hardware manufacturers to support open
source development.
Linux has only a small market share, but it's slowly growing.
Linux driver support does sometimes influence the decision which
hardware to buy.
With NdisWrapper, the hardware manufacturer can say:
"Our hardware is supported through the open source NdisWrapper."
Without NdisWrapper, they will sometimes hear that people did choose to
buy hardware from a different hardware manufacturer that has a Linux
driver. This can make the hardware manufacturer more friendly towards
open source development (e.g. by providing hardware specs).
Secondly, binary-only drivers have an impact on the stability of the
Linux kernel.
E.g. during the last years the nvidia has produced relatively many
kernel crashes - and I doubt that binary-only drivers for Windows are
much better in this respect.
The users only see their kernel crashing blaming the Linux kernel and
harming the reputation of the stability of Linux.
> Lee
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-08-08 23:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 19:22 Wireless support Lee Revell
2005-08-07 19:56 ` Lee Revell
2005-08-08 5:50 ` Martin J. Bligh
2005-08-08 17:57 ` Lee Revell
2005-08-08 0:39 ` Alejandro Bonilla Beeche
2005-08-08 1:20 ` Lee Revell
2005-08-08 1:29 ` Alejandro Bonilla Beeche
2005-08-08 6:31 ` Denis Vlasenko
2005-08-08 17:48 ` Lee Revell
2005-08-08 17:51 ` Arjan van de Ven
2005-08-08 18:13 ` Andreas Steinmetz
2005-08-08 18:19 ` Lee Revell
2005-08-08 18:24 ` Andreas Steinmetz
2005-08-08 18:27 ` Lee Revell
2005-08-08 18:56 ` Alejandro Bonilla
2005-08-08 19:06 ` Lee Revell
2005-08-08 19:55 ` alan
2005-08-08 23:29 ` Adrian Bunk [this message]
2005-08-08 23:43 ` Alejandro Bonilla Beeche
2005-08-09 9:09 ` Jochen Friedrich
2005-08-09 13:52 ` Kyle Moffett
2005-08-09 14:24 ` Rafael J. Wysocki
2005-08-09 16:09 ` Jochen Friedrich
2005-08-12 2:40 ` Lee Revell
2005-08-12 2:59 ` roucaries bastien
2005-08-12 3:17 ` Lee Revell
2005-08-12 4:18 ` Kyle Moffett
2005-08-08 19:27 ` linux-os (Dick Johnson)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050808232957.GR4006@stusta.de \
--to=bunk@stusta.de \
--cc=abonilla@linuxwireless.org \
--cc=arjan@infradead.org \
--cc=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=vda@ilport.com.ua \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.