From: "David Schwartz" <davids@webmaster.com>
To: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: RE: Will there be Intel Wireless 3945ABG support?
Date: Wed, 12 Jul 2006 15:09:22 -0700 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKKEEONCAB.davids@webmaster.com> (raw)
In-Reply-To: <44B443E4.1000707@linux.intel.com>
> Also if the binary only chunk of code is neccessary to make the open
> source bit work then its a derivative work as I understand the
> situation,
The issue is not whether the userspace daemon is a derivative work of any
GPL'd work and therefore must be covered. The issue is whether the kernel
driver and the userspace program are one work or two. If neither is any use
without the other, and the two were designed together, it seems implausible
to argue that they are two works.
A boundary that consists of an API that allows the work on either side to
be interchanged with others and the other work still operate substantially
the same can certainly divide two works. That's why a C program that uses
the standard library can be a separate work from the standard library. Any C
program works with that library, and the library works with any C program.
A boundary custom designed for these two programs, and which is not
intended to allow either program to be replaced with another, would not seem
to do the job.
DS
next prev parent reply other threads:[~2006-07-12 22:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 16:32 Joseph Michael Smidt
2006-07-11 16:47 ` Otavio Salvador
2006-07-11 17:12 ` John W. Linville
2006-07-11 18:09 ` Alistair John Strachan
2006-07-11 18:25 ` Alon Bar-Lev
2006-07-11 18:43 ` Alistair John Strachan
2006-07-11 18:55 ` Alan Cox
2006-07-11 19:18 ` Matthieu CASTET
2006-07-11 20:22 ` Daniel Bonekeeper
2006-07-11 22:22 ` Matthew Garrett
2006-07-11 23:54 ` H. Peter Anvin
2006-07-12 0:04 ` Matthew Garrett
2006-07-12 0:35 ` James Ketrenos
2006-07-12 1:19 ` David Miller
2006-07-12 11:30 ` Alan Cox
2006-07-12 17:17 ` Alon Bar-Lev
2006-07-12 22:09 ` David Schwartz [this message]
2006-07-11 20:16 ` Thorsten Kranzkowski
2006-07-12 0:42 ` Thomas Tuttle
2006-07-12 0:57 ` H. Peter Anvin
2006-07-12 1:10 ` David Miller
2006-07-12 1:15 ` Valdis.Kletnieks
2006-07-12 8:19 ` Alistair John Strachan
2006-07-12 8:23 ` Alistair John Strachan
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=MDEHLPKNGKAHNMBLJOLKKEEONCAB.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®