mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Hell.Surfers@cwctv.net>
To: david.lang@digitalinsight.com, paul@clubi.ie,
	riel@conectiva.com.br, linux-kernel@vger.kernel.org, rms@gnu.org
Subject: RE:Re: Why is Nvidia given GPL'd code to use in closed source drivers?
Date: Thu, 2 Jan 2003 06:16:31 +0000	[thread overview]
Message-ID: <0a5713612060213DTVMAIL4@smtp.cwctv.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 179 bytes --]

in a way, yes.

Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].

On Wed, 1 Jan 2003 17:08:26 -0800 (PST) David Lang <david.lang@digitalinsight.com> wrote:

[-- Attachment #2: Type: message/rfc822, Size: 4183 bytes --]

From: David Lang <david.lang@digitalinsight.com>
To: Paul Jakma <paul@clubi.ie>
Cc: Rik van Riel <riel@conectiva.com.br>, Hell.Surfers@cwctv.net,  linux-kernel@vger.kernel.org, rms@gnu.org
Subject: Re: Why is Nvidia given GPL'd code to use in closed source drivers?
Date: Wed, 1 Jan 2003 17:08:26 -0800 (PST)
Message-ID: <Pine.LNX.4.44.0301011706400.21656-100000@dlang.diginsite.com>

well libc uses the kernel headers and basicly all userspace programs use
libc so that makes oracle a derivitive work of the kernel??????

luckly that's not how things actually work.

David Lang

On Thu, 2 Jan 2003, Paul Jakma wrote:

> Date: Thu, 2 Jan 2003 00:31:13 +0000 (GMT)
> From: Paul Jakma <paul@clubi.ie>
> To: Rik van Riel <riel@conectiva.com.br>
> Cc: Hell.Surfers@cwctv.net, linux-kernel@vger.kernel.org, rms@gnu.org
> Subject: Re: Why is Nvidia given GPL'd code to use in closed source
>     drivers?
>
> On Wed, 1 Jan 2003, Rik van Riel wrote:
>
> > Copyright law is pretty explicit about the situations the GPL
> > applies to.  If something can be reasonably considered to be a
> > "derivative work" of a GPL work, the GPL applies and the new work
> > needs to be GPL.
>
> and:
>
> > but only a song.  If nvidia's driver only uses some simple
> > declarations from include files and no large (>7 lines? >10lines?
> > what's large?) inline functions AND the nvidia driver uses only the
> > standard interfaces to hook into the Linux kernel, then it's not a
> > derivative work and nvidia gets to choose the license.
>
> It has long been held that linking to GPL code is suffient to
> consitute 'derived work' status, hence the existence of the LGPL.
>
> The NVidia shim makes use of several kernel subsystems, the PCI
> device layer, the VM, the module system (well really, the kernel
> makes of use of the functions the module provides :) ), IRQ
> subsystem, the VFS, etc.. These systems are rather large bodies of
> code - without which the NVidia kernel driver could not work.
>
> So I am not quite sure on what basis one could argue the NVidia
> driver is not a derivative work, and hence it seems to me the NVidia
> driver is technically in material breach of GPL.
>
> You seem to be basing your opinion on:
>
>  "the nvidia driver uses only the standard interfaces to hook into
>  the Linux kernel"
>
> How are the standard interfaces not covered by the GPL?
>
> I know Linus' has often posted to l-k that he doesnt care about
> binary only modules as long as they stick to the exported interfaces.
> However, are all the kernel developers agreed on this? And if so, can
> this exception be formalised and put into the COPYING file? If not,
> then is NVidia not in breach of the kernel's licence?
>
> > Rik
>
> regards,
> --
> Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
> 	warning: do not ever send email to spam@dishone.st
> Fortune:
> Programmers do it bit by bit.
>
> -
> 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/
>

             reply	other threads:[~2003-01-02  6:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02  6:16 Hell.Surfers [this message]
2003-01-02  6:34 ` [OT] " Milosz Tanski
2003-01-02 13:28   ` Paul Jakma
2003-01-02 17:37   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-01-08 16:26 Hell.Surfers
2003-01-05  6:14 Hell.Surfers
2003-01-02 17:39 Hell.Surfers
2003-01-02  6:25 Hell.Surfers
2003-01-02  6:14 Hell.Surfers
2003-01-02  6:04 Hell.Surfers
2003-01-02  5:37 Hell.Surfers
2003-01-02 21:42 ` Rik van Riel
2003-01-02  5:33 Hell.Surfers
2003-01-03 13:02 ` NEURONET
2003-01-01 18:10 Hell.Surfers
2003-01-01  5:51 Hell.Surfers
2003-01-01  5:46 ` David Lang
2003-01-01  7:43 ` Andre Hedrick
2003-01-01  5:45 RE:Re: " Hell.Surfers
2003-01-01  5:55 ` A Guy Called Tyketto
2003-01-01  5:30 Hell.Surfers
2003-01-01  5:51 ` A Guy Called Tyketto
2003-01-01  5:08 Hell.Surfers
2003-01-01  5:01 Hell.Surfers
2003-01-01  1:51 Hell.Surfers

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=0a5713612060213DTVMAIL4@smtp.cwctv.net \
    --to=hell.surfers@cwctv.net \
    --cc=david.lang@digitalinsight.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@clubi.ie \
    --cc=riel@conectiva.com.br \
    --cc=rms@gnu.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®