From: "David Schwartz" <davids@webmaster.com>
To: "Dave Neuer" <mr.fred.smoothie@pobox.com>,
"Phillip Susi" <psusi@cfl.rr.com>
Cc: "Luke-Jr" <luke@dashjr.org>,
"Anshuman Gholap" <anshu.pg@gmail.com>,
<linux-kernel@vger.kernel.org>
Subject: RE: [future of drivers?] a proposal for binary drivers.
Date: Thu, 9 Mar 2006 20:25:22 -0800 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKCEBLKKAB.davids@webmaster.com> (raw)
In-Reply-To: <4410EAFF.9050509@cfl.rr.com>
> The key question is does work A contain substantial parts of work B?
> In the case of a source library that is compiled and linked into an
> executable, then you can argue that the executable image is a work
> substantially derived from the library. In the case of linking to a
> shared object however, the binary does not actually contain any of the
> material from the library, so it is not a derived work.
Not just substantial parts, but substantial *creative* (as opposed to
functional) parts. Furthermore, are those parts combined with the work in a
*creative* way. (Otherwise you have two works in aggregate form, not a
single derived work.)
I would argue that linking creates aggregate works just as tar does. The
key *legal* issue is whether the combination is mechanical or creative.
> In the case of ATI's drivers at least, they distribute their own object
> files which they hold the copyright to, and are not derived from the
> linux kernel in any way, and the user must link them with the correct
> objects of kernel code to create the actual loadable module. At best if
> you could show that the final module contains substantial code from the
> kernel you might argue that it is a derived work, but since ATI only
> distributes their own object code, there's no way you can claim they are
> infringing on your copyright.
I think that argument would fail anyway. It would require you to argue that
making an actual loadable module from the Linux kernel source and its header
files was not the normal use of those header files. I think that argument
would fail the giggle test.
RedHat, for example, distributes a 'kernel-devel' package whose primary
purpose is to allow you to turn module source code into module executables.
Since you have the right to normal use without agreeing to the GPL (under at
least first sale), you can *create* those binary modules without agreeing to
the GPL. Remember, there is no right under copyright to specifically
restrict the *distribution* of derivative works, it relies upon you needing
the GPL to give you the right to make the derived work in the first place.
DS
next prev parent reply other threads:[~2006-03-10 4:25 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 9:35 Anshuman Gholap
2006-03-08 9:51 ` Jan Knutar
2006-03-08 10:03 ` Anshuman Gholap
2006-03-08 10:23 ` Martin Mares
2006-03-08 14:34 ` Jan Engelhardt
2006-03-08 11:11 ` Jan Knutar
2006-03-08 13:07 ` Diego Calleja
2006-03-09 15:17 ` Luke-Jr
2006-03-09 16:22 ` Phillip Susi
2006-03-09 16:56 ` Michael Concannon
2006-03-09 9:21 ` Helge Hafting
2006-03-10 8:03 ` Matthias Andree
2006-03-13 23:06 ` Bernd Petrovitsch
2006-03-14 0:00 ` David Schwartz
2006-03-15 0:50 ` Valdis.Kletnieks
2006-03-15 9:18 ` Bernd Petrovitsch
2006-03-08 19:41 ` Martin Michlmayr
2006-03-08 9:57 ` Xavier Bestel
2006-03-08 10:27 ` Al Viro
2006-03-08 10:52 ` Anshuman Gholap
2006-03-08 10:55 ` Arjan van de Ven
2006-03-08 11:02 ` Anshuman Gholap
2006-03-14 3:02 ` Jon Masters
[not found] ` <20060313223520.113bc6d0.seanlkml@sympatico.ca>
2006-03-14 3:35 ` sean
2006-03-08 11:40 ` Matthias Schniedermeyer
2006-03-08 12:00 ` Anshuman Gholap
2006-03-09 15:32 ` Rik van Riel
2006-03-08 14:59 ` Dave Neuer
2006-03-08 21:54 ` Hannu Savolainen
2006-03-09 4:41 ` David Schwartz
2006-03-09 10:02 ` Dave Airlie
2006-03-09 10:42 ` Rudolf Randal
2006-03-09 11:22 ` DervishD
2006-03-09 12:13 ` Andreas Mohr
2006-03-09 18:34 ` Alistair John Strachan
2006-03-10 8:19 ` DervishD
2006-03-09 22:04 ` David Schwartz
2006-03-09 11:41 ` Dagfinn Ilmari Mannsåker
2006-03-09 22:12 ` David Schwartz
2006-03-09 15:13 ` Dave Neuer
2006-03-09 22:11 ` David Schwartz
2006-03-09 23:30 ` Dave Neuer
2006-03-10 1:04 ` David Schwartz
2006-03-09 9:26 ` Helge Hafting
2006-03-09 15:09 ` Luke-Jr
2006-03-09 16:29 ` Phillip Susi
2006-03-09 16:49 ` Olivier Galibert
2006-03-09 17:33 ` Dave Neuer
2006-03-09 18:25 ` Xavier Bestel
2006-03-09 20:22 ` Dave Neuer
2006-03-09 21:32 ` marty fouts
2006-03-11 0:54 ` Eduard Bloch
2006-03-11 1:01 ` Jan Knutar
2006-03-11 9:16 ` DervishD
2006-03-11 9:52 ` Eduard Bloch
2006-03-11 11:43 ` David Schwartz
2006-03-11 12:07 ` DervishD
2006-03-12 17:09 ` Dave Neuer
2006-03-13 2:19 ` David Schwartz
2006-03-13 16:16 ` Dave Neuer
2006-03-13 21:57 ` David Schwartz
2006-03-14 13:30 ` Helge Hafting
2006-03-12 3:57 ` Dave Neuer
2006-03-13 5:16 ` David Schwartz
2006-03-13 5:25 ` David Schwartz
2006-03-13 8:20 ` Arjan van de Ven
2006-03-13 21:57 ` David Schwartz
[not found] ` <20060314032447.6be9af0a.seanlkml@sympatico.ca>
2006-03-14 8:24 ` sean
2006-03-14 10:46 ` David Schwartz
2006-03-14 21:42 ` Valdis.Kletnieks
2006-03-13 9:24 ` Bernd Petrovitsch
2006-03-13 17:16 ` Lee Revell
2006-03-13 22:08 ` Bernd Petrovitsch
2006-03-13 21:57 ` David Schwartz
2006-03-09 20:15 ` Phillip Susi
2006-03-09 21:30 ` Dave Neuer
2006-03-09 22:06 ` Lee Revell
2006-03-10 2:57 ` Phillip Susi
2006-03-10 4:25 ` David Schwartz [this message]
2006-03-09 22:21 ` David Schwartz
2006-03-08 21:28 Tim Tassonis
2006-03-08 21:32 ` Randy.Dunlap
2006-03-09 0:20 ` Jan Knutar
2006-03-13 11:17 ` Helge Hafting
2006-03-13 15:19 ` Anshuman Gholap
2006-03-13 15:53 ` Dave Neuer
2006-03-13 6:02 Matt Reuther
2006-03-13 9:08 ` Bernd Petrovitsch
2006-03-13 22:00 ` David Schwartz
2006-03-13 22:32 ` Lee Revell
2006-03-14 0:02 ` David Schwartz
2006-03-13 19:00 Tim Tassonis
2006-03-13 19:15 ` Lee Revell
2006-03-13 19:25 ` Tim Tassonis
2006-03-13 19:31 ` Lee Revell
2006-03-13 19:46 ` Tim Tassonis
2006-03-13 23:06 ` Bernd Petrovitsch
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=MDEHLPKNGKAHNMBLJOLKCEBLKKAB.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=anshu.pg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@dashjr.org \
--cc=mr.fred.smoothie@pobox.com \
--cc=psusi@cfl.rr.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
all inboxes | Powered by JetHome®