public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Craig Milo Rogers <rogers@isi.edu>
To: Rob van Nieuwkerk <robn@berrymount.nl>
Cc: Wouter Van Hemel <wouter-kernel@fort-knox.rave.org>,
	prakashkc@gmx.de, vda@port.imtp.ilyichevsk.odessa.ua,
	linux-kernel@vger.kernel.org
Subject: Re: kernel 2.6.8 pwc patches and counterpatches
Date: Fri, 27 Aug 2004 17:50:03 -0700	[thread overview]
Message-ID: <20040828005003.GJ24018@isi.edu> (raw)
In-Reply-To: <20040828011818.2d5f282c.robn@berrymount.nl>

On 04.08.28, Rob van Nieuwkerk wrote:
> 	The author of the pwc driver has publicly stated that this
> 	NDA has expired more than 1 year ago !!!
> 
> Despite this he refuses to release the source code for the binary-only
> driver.  Of course it is his right to do so: it is his code.
> But I think it is important for everyone to know this fact.

	I agree that everyone should know this.  It shows remarkable
integrity and restraint on Nemosoft's part, and is, I feel, in
concordance with the values that Linux recently expressed in his
message regarding the GPL and lawyers.

	In one of Nemosoft's messages, he said that we wasn't
releasing proprietary data on the Philips chips, even though his NDA
has expired, because (and I'm paraphrasing here) he wants to maintain
a good working relationship with Philips.  I believe that this is an
important point, and a critical one for long-term success.  We, the
Linux community, should want Philips to voluntarily release the
details on their chips.  This is important because we should want
Philips to release *new* programming details on *new* chips in a
timely fashion; preferably, in an open-source-conformant fashion.

	As you can see, if Nemosoft were to unilaterally breach
Philips' confidence in him, then Philips might stop telling him the
programming details on new chips.  Linux would potentially have
working open source drivers for older chips, but potentially no
drivers at all, open or closed source, for new chips by this
manufacturer.

					Craig Milo Rogers

  parent reply	other threads:[~2004-08-28  0:58 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 14:31 kernel 2.6.8 pwc patches and counterpatches city_hunter
2004-08-26 18:25 ` Wouter Van Hemel
     [not found]   ` <20040826190701.GA13310@kroah.com>
2004-08-26 23:35     ` Wouter Van Hemel
2004-08-26 23:40       ` Greg KH
2004-08-27  0:21         ` Wouter Van Hemel
     [not found]           ` <200408270917.47656.vda@port.imtp.ilyichevsk.odessa.ua>
2004-08-27 12:47             ` Wouter Van Hemel
2004-08-27 12:58               ` Xavier Bestel
2004-08-27 13:30                 ` Wouter Van Hemel
2004-08-27 13:04               ` Denis Vlasenko
2004-08-27 13:13                 ` Prakash K. Cheemplavam
2004-08-27 13:44                   ` Wouter Van Hemel
2004-08-27 23:18                     ` Rob van Nieuwkerk
2004-08-28  0:03                       ` Denis Vlasenko
2004-08-28  0:19                         ` James Courtier-Dutton
2004-08-28  0:50                       ` Craig Milo Rogers [this message]
2004-08-27 16:46                   ` Lee Revell
2004-08-27 13:35                 ` Wouter Van Hemel
2004-08-27  9:25   ` Christoph Hellwig
2004-08-27 12:56     ` Wouter Van Hemel
     [not found]   ` <buok6vldx4l.fsf@mctpc71.ucom.lsi.nec.co.jp>
2004-08-27 12:38     ` Wouter Van Hemel
     [not found]   ` <200408270845.38015.vda@port.imtp.ilyichevsk.odessa.ua>
2004-08-27 12:44     ` Wouter Van Hemel
2004-08-27 13:41       ` Paulo Marques
2004-08-27 13:58         ` Wouter Van Hemel
  -- strict thread matches above, loose matches on Subject: below --
2004-08-28  3:50 Thomas Winischhofer
2004-08-27 16:46 David McBride
2004-08-27 16:26 Kenneth Lavrsen
2004-08-27 16:51 ` Christoph Hellwig
2004-08-27 17:01 ` Greg KH
2004-08-27 17:34 ` Xavier Bestel
2004-08-27 18:09   ` David Woodhouse
2004-08-27 18:35     ` Vojtech Pavlik
2004-08-27 20:47       ` David Woodhouse
2004-08-27 21:18         ` Kenneth Lavrsen
2004-08-28 16:22   ` Brian Beattie
2004-08-27 18:08 ` Denis Vlasenko
2004-08-29 13:25 ` Alan Cox
2004-08-27 14:07 Thomas Winischhofer
2004-08-27 20:01 ` David S. Miller
2004-08-28  3:03   ` Thomas Winischhofer
2004-08-28  6:55     ` Arjan van de Ven
2004-08-28 14:46       ` Thomas Winischhofer
2004-08-28 17:13         ` Thomas Winischhofer
2004-08-29 13:28       ` Alan Cox
2004-08-29 15:00         ` Thomas Winischhofer
     [not found] <1092793392.17286.75.camel@localhost>
     [not found] ` <1092845135.8044.22.camel@localhost>
     [not found]   ` <20040823221028.GB4694@kroah.com>
2004-08-24 22:58     ` Nemosoft Unv.
2004-08-24 23:04       ` Greg KH
2004-08-25 14:02       ` Simon Oosthoek
2004-08-26  0:55       ` Rob van Nieuwkerk
2004-08-26  1:27         ` Rob van Nieuwkerk
2004-08-26  9:00       ` syrius.ml

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=20040828005003.GJ24018@isi.edu \
    --to=rogers@isi.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prakashkc@gmx.de \
    --cc=robn@berrymount.nl \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=wouter-kernel@fort-knox.rave.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox