Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S129667AbRBSL3b>; Mon, 19 Feb 2001 06:29:31 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S129804AbRBSL3L>; Mon, 19 Feb 2001 06:29:11 -0500
Received: from femail12.sdc1.sfba.home.com ([24.0.95.108]:8146 "EHLO
	femail12.sdc1.sfba.home.com") by vger.kernel.org with ESMTP
	id <S129667AbRBSL3J>; Mon, 19 Feb 2001 06:29:09 -0500
Message-ID: <003b01c09a67$29367e40$8d19b018@c779218a>
From: "Nicholas Knight" <tegeran@home.com>
To: "Jeff Garzik" <jgarzik@mandrakesoft.com>
Cc: <linux-kernel@vger.kernel.org>
In-Reply-To: <Pine.LNX.3.96.1010219050514.17784G-100000@mandrakesoft.mandrakesoft.com>
Subject: Re: [LONG RANT] Re: Linux stifles innovation...
Date: Mon, 19 Feb 2001 03:28:56 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

----- Original Message -----
From: "Jeff Garzik" <jgarzik@mandrakesoft.com>
To: "Werner Almesberger" <Werner.Almesberger@epfl.ch>
Cc: "Henning P. Schmiedehausen" <hps@tanstaafl.de>;
<linux-kernel@vger.kernel.org>
Sent: Monday, February 19, 2001 3:07 AM
Subject: Re: [LONG RANT] Re: Linux stifles innovation...


> On Mon, 19 Feb 2001, Werner Almesberger wrote:
> > Now what's at stake ? Look at the Windows world. Also there, companies
> > could release their drivers as Open Source. Quick, how many do this ?
> > Almost none. So, given the choice, most companies have defaulted to
> > closed source. Consistently complaining when a company tries to release
> > only closed source drivers for Linux seems to generally have the desired
> > effect of making them change their policy.
>
> FWIW, -every single- Windows driver source code I've seen has been
> bloody awful.  Asking them to release that code would probably result in
> embarrassment.  Same reasoning why many companies won't release hardware
> specifications...  The internal docs are bad.  Really bad.

While I understand that internal docs and source are often simply a mess, I
fail to see why this should prevent a company from releasing specs or
source.
Sure somebody will come along and say "What on earth were you people
THINKING?!", and then they'll get over it and do something useful with the
specs and/or source to the drivers (or if they don't, somebody else will)
I seriously doubt it'd lead to a company seeing a drop in sales because of
it... and even if they did, I'd say it's a calculated risk, as they could
well pick up a higher number of new customers than the number of old
customers they lost due to wider ranging support.
And even if their specs and code were the worst peices of trash on the
planet, I'd still thank them for opening them up to the public.

-NK

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