From: Dave Jones <davej@codemonkey.org.uk>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: jamesbuch@iprimus.com.au,
Rik van Riel <riel@imladris.surriel.com>,
Tomas Szepe <szepe@pinerecords.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux kernel rant
Date: Fri, 21 Feb 2003 15:34:48 +0000 [thread overview]
Message-ID: <20030221153447.GH22285@codemonkey.org.uk> (raw)
In-Reply-To: <3E563D53.8020102@nortelnetworks.com>
On Fri, Feb 21, 2003 at 09:53:07AM -0500, Chris Friesen wrote:
> I think what you're missing is that many drivers are *written* under an
> NDA but then the resulting code is released under an open license.
>
> You're free to use the resulting driver, but the writer can't talk about
> exactly how it works.
This last part varies between NDA/vendors. Some of them are just simply
"These docs are just for you, read them, do what you will, just
don't redistribute them in whole or in part". Some are a little
more restricting but those are few and far between in my experience.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2003-02-21 15:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 4:51 Linux kernel rant James Buchanan
2003-02-20 17:22 ` Jeff Garzik
2003-02-20 17:26 ` Tomas Szepe
2003-02-21 5:42 ` James Buchanan
2003-02-20 17:45 ` Tomas Szepe
2003-02-21 5:54 ` James Buchanan
2003-02-20 18:15 ` Tomas Szepe
2003-02-21 6:23 ` James Buchanan
2003-02-20 18:20 ` Rik van Riel
2003-02-21 6:24 ` James Buchanan
2003-02-20 17:54 ` Rik van Riel
2003-02-21 6:01 ` James Buchanan
2003-02-20 18:09 ` Rik van Riel
2003-02-21 6:17 ` James Buchanan
2003-02-20 18:19 ` Rik van Riel
2003-02-20 18:20 ` Tomas Szepe
2003-02-21 6:25 ` James Buchanan
2003-02-21 14:53 ` Chris Friesen
2003-02-21 15:34 ` Dave Jones [this message]
2003-02-20 18:22 ` Jeff Garzik
2003-02-21 6:29 ` James Buchanan
2003-02-20 18:02 ` Jeff Garzik
2003-02-21 6:21 ` James Buchanan
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=20030221153447.GH22285@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=cfriesen@nortelnetworks.com \
--cc=jamesbuch@iprimus.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@imladris.surriel.com \
--cc=szepe@pinerecords.com \
/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