Message-ID: <48610C90.5020004@davidnewall.com>
Date: Wed, 25 Jun 2008 00:32:40 +0930
From: David Newall <davidn@davidnewall.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080227)
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Position Statement on Linux Kernel Modules
References: <20080623050118.GA22852@kroah.com> <20080623112934.GC5713@hp0.dynamicro.ca> <20080623130917.GB1369@1wt.eu> <20080624113347.GA5246@hp0.dynamicro.ca>
In-Reply-To: <20080624113347.GA5246@hp0.dynamicro.ca>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1514
Lines: 31

Greg Louis wrote:
> Willy Tarreau wrote
>>> (Of course, the best way to rebut that argument [ that outside the
>>> developer community, nobody cares whether drivers are proprietary ]
>>> would be for end-users to vote with their feet, but for a lot of
>>> us, me included, that's not a practical option.)
>>>       
>> The problem is exactly what you describe in your last sentence. Hardware
>> manufacturers are well aware of that and make no effort to provide correct
>> drivers when they (think they) have a monopoly in certain areas.
>>
>> What would be needed would be a public list of alternative hardware for
>> known existing hardware.
>
> That is Utopian, I fear.  For example, what notebook supports the
> installation of alternative hardware?

Yet, in non-mobile platforms, alternative hardware is sometimes an
option, and so the suggestion does have utility.  But it's use goes
beyond those situations, as it engenders a new mindset amongst
manufacturers, a mindset in which they have to play by our rules or lose
market share, and once they start doing that they'll find there's no
reason not to keep doing it.  Then, even mobile platforms will have a
full set of open drivers.

So I think a public list of alternative hardware is an excellent suggestion.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/