mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: "Jeff V. Merkey" <jmerkey@utah-nac.org>
Cc: alex@alexfisher.me.uk, linux-kernel@vger.kernel.org
Subject: Re: Would I be violating the GPL?
Date: Tue, 1 Nov 2005 19:15:49 +0000	[thread overview]
Message-ID: <200511011915.49480.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <43679B22.8070905@utah-nac.org>

On Tuesday 01 November 2005 16:43, Jeff V. Merkey wrote:
> 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 you even take 2 minutes to actually inspect the NVIDIA video driver sources 
(extract the .run file with --extract-only, and cd to usr/src/nv) you'll find 
the "glue" which is provided as source, but not under the GPL, does indeed 
#include kernel headers at compile time.

It does not distribute them, however, but it is completely nonsensical to 
class this as having "no dependency". It has a compile time and runtime 
dependency on the current kernel. What driver wouldn't?

> 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.

There's clearly a grey area here, but I have no understanding of the law so I 
will not comment beyond stating fact. But you are at least wrong about the 
NVIDIA driver.

-- 
Cheers,
Alistair.

'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

  reply	other threads:[~2005-11-01 19:15 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 17:49 Alexander Fisher
2005-11-01 16:43 ` Jeff V. Merkey
2005-11-01 19:15   ` Alistair John Strachan [this message]
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
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=200511011915.49480.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=alex@alexfisher.me.uk \
    --cc=jmerkey@utah-nac.org \
    --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®