From: "Jeff V. Merkey" <jmerkey@utah-nac.org>
To: alex@alexfisher.me.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: Would I be violating the GPL?
Date: Tue, 01 Nov 2005 09:43:14 -0700 [thread overview]
Message-ID: <43679B22.8070905@utah-nac.org> (raw)
In-Reply-To: <5449aac20511010949x5d96c7e0meee4d76a67a06c01@mail.gmail.com>
Alan Cox and others have publicly stated that drivers, if complied stand
alone with NO DEPENDENCIES ON KERNEL HEADERS (i.e. they do not
incorporate in any way any kernel headers or source code tagged GPL) do
not violate the GPL when provided with Linux. DSFS, NVidia, and several
folks build kernel modules which are stand alone and are not objected to
by the majority of folks.
If these drivers include kernel headers as part of the build, then the
drivers violate the GPL. Period. Check the code. If the vendor is
including **ANY** GPL kernel headers, then they are required to open
source the drivers. There are some zealots and GPL bigots that disagree
with this, but Linux folks seem to be reasonable on this point.
Jeff
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.
>>From what I have read, this concern is only valid if the binary module
>is considered to be a 'derived work' of the kernel. The module source
>directly includes the following kernel headers :
>
>#include <linux/kernel.h>
>#include <linux/types.h>
>#include <linux/fs.h>
>#include <linux/errno.h>
>#include <linux/wrapper.h>
>#include <linux/module.h>
>#include <linux/iobuf.h>
>#include <linux/highmem.h>
>#include <asm/uaccess.h>
>#include <linux/mm.h>
>#include <asm/unistd.h>
>
>Does this make the compiled module a derived work? Are the 'static
>inlines' from the headers substantial enough?
>
>I really want to have a clear understanding of the issues before
>contacting the supplier. Any advice would be very much appreciated.
>Kind regards,
>Alex
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
next prev parent reply other threads:[~2005-11-01 18:05 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 [this message]
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
-- 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=43679B22.8070905@utah-nac.org \
--to=jmerkey@utah-nac.org \
--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