From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: alex@alexfisher.me.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: Would I be violating the GPL?
Date: Thu, 03 Nov 2005 12:44:07 +0000 [thread overview]
Message-ID: <1131021847.18848.20.camel@localhost.localdomain> (raw)
In-Reply-To: <5449aac20511010949x5d96c7e0meee4d76a67a06c01@mail.gmail.com>
On Maw, 2005-11-01 at 17:49 +0000, Alexander Fisher wrote:
> Hello.
>
> A supplier of a PCI mezzanine digital IO card has provided a linux 2.4
> driver as source code. They have provided this code source with a
> license stating I won't redistribute it in anyway.
> My concern is that if I build this code into a module, I won't be able
> to distribute it to customers without violating either the GPL (by not
> distributing the source code), or the proprietary source code license
> as currently imposed by the supplier.
You need to ask a lawyer in the part of the world you plan to do this.
The area of law in question is quite murky and at the moment there is no
direct linux kernel caselaw of relevance that helps (at least that i
know of).
I suspect all kernel modules are probably derivative works but I am not
a lawyer and when you look at code which is large, shared with other
OS's and uses minimal kernel services it gets more complex.
For user space it isn't a problem and the kernel specifically clarifies
this in the copyright notice so as to avoid confusion or risk.
There is a second consideration however - your module will work only
with the exact gcc/kernel/options configuration you selected. That makes
binary modules problematic anyway as the kernel has an API not an ABI.
It would be far better to understand what the suppliers concern is and
to see if you can find an amicable way to distribute a GPL driver or
even get it into the base kernel that does not cause concerns for the
vendor. You may find the linux lab project and other digital I/O cards
with open drivers useful in persuading them of course ;)
next prev parent reply other threads:[~2005-11-03 12:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 17:49 Would I be violating the GPL? Alexander Fisher
2005-11-01 16:43 ` Jeff V. Merkey
2005-11-01 19:15 ` Alistair John Strachan
2005-11-16 15:26 ` David Schwartz
2005-11-16 16:39 ` Jeffrey V. Merkey
2005-11-01 20:32 ` Rob Landley
2005-11-01 20:46 ` Arjan van de Ven
2005-11-01 19:00 ` Michael Buesch
2005-11-01 17:44 ` Jeff V. Merkey
2005-11-01 19:12 ` Michael Buesch
2005-11-01 20:46 ` Alexander Fisher
2005-11-01 21:06 ` linux-os (Dick Johnson)
2005-11-02 9:49 ` Giuliano Pochini
2005-11-02 14:54 ` Alex Lyashkov
2005-11-02 15:29 ` Nix
2005-11-02 15:42 ` Alex Lyashkov
2005-11-02 16:16 ` linux-os (Dick Johnson)
2005-11-02 17:26 ` Nix
2005-11-02 15:55 ` Giuliano Pochini
2005-11-10 19:02 ` Jan Engelhardt
2005-11-10 19:12 ` Lennart Sorensen
2005-11-17 21:23 ` Jan Engelhardt
2005-11-18 15:19 ` Lennart Sorensen
2005-11-18 15:25 ` Jan Engelhardt
2005-11-18 21:55 ` Petr Vandrovec
2005-11-01 22:04 ` Rob Landley
2005-11-01 19:58 ` Lee Revell
2005-11-01 20:30 ` Jeff V. Merkey
2005-11-01 20:57 ` Alexander Fisher
2005-11-02 16:12 ` Stuart MacDonald
2005-11-03 12:44 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-02 22:21 linux
2005-11-02 22:47 ` linux-os (Dick Johnson)
2005-11-03 3:50 ` Rob Landley
2005-11-04 0:57 ` Horst von Brand
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=1131021847.18848.20.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alex@alexfisher.me.uk \
--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