From: "Stuart MacDonald" <stuartm@connecttech.com>
To: <alex@alexfisher.me.uk>, <linux-kernel@vger.kernel.org>
Subject: RE: Would I be violating the GPL?
Date: Wed, 2 Nov 2005 11:12:27 -0500 [thread overview]
Message-ID: <049c01c5dfc8$37e3b3d0$294b82ce@stuartm> (raw)
In-Reply-To: <5449aac20511010949x5d96c7e0meee4d76a67a06c01@mail.gmail.com>
From: Alexander Fisher [alexjfisher@gmail.com]
> 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.
It seems to me that the supplier is violating the GPL.
They've distributed a linux driver.
There are rare exceptions, but most linux drivers are considered
derived works of the kernel and must also be licenced under the GPL
(GPL 2.b).
As such, further restrictions on the rights that come with the driver
are prohibited (GPL 6.). Or, this may count as sublicencing, which is
also prohibited (GPL 4.).
So their licence prohibiting redistribution is in violation of the GPL.
Since no one else has commented on this, I'm wondering if I'm wrong.
Comments?
If I'm right, I believe that GPL 4. allows you to proceed with the
driver as per the GPL...
> My concern is that if I build this code into a module, I won't be able
> to distribute it to customers
..and you can redistribute it.
> without violating either the GPL (by not
> distributing the source code), or the proprietary source code license
> as currently imposed by the supplier.
In my mind, this is exactly what the GPL is designed to prevent.
..Stu
next prev parent reply other threads:[~2005-11-02 16:12 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 [this message]
2005-11-03 12:44 ` Alan Cox
-- 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='049c01c5dfc8$37e3b3d0$294b82ce@stuartm' \
--to=stuartm@connecttech.com \
--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