public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Disconnect <dc.disconnect@gmail.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: jp@enix.org, linux-kernel@vger.kernel.org
Subject: Re: Possible GPL infringement in Broadcom-based routers
Date: Fri, 5 Nov 2004 13:58:23 -0500	[thread overview]
Message-ID: <55f6199c041105105861a25172@mail.gmail.com> (raw)
In-Reply-To: <200411061040.iA6AeZp03452@freya.yggdrasil.com>

(IANAL)

User's can't violate the GPL. Only distributers can. (If said user is
shipping around copies of the integrated kernel+module - ram images,
in this case - they become a distributer.)

Just to reiterate, since this comes up a lot....

You can do WHATEVER you want on your box, with GPL code. You can (as I
recall) even run paid services (web services, for example) on modified
GPL code without releasing any sources. The GPL only covers
-DISTRIBUTION-. As soon as the modified BINARY gets distributed, the
GPL comes into play. Until that happens, there is NO RESTRICTION.

As far as Broadcom (and Tivo, and Linksys, and Sharp, and....) the
only questions are whether the driver is shipped as a module, and
whether or not the majority of the driver existed in a similar,
non-Linux form before integration. (If its not a module, they are
distributing a modified kernel. If it was written specifically for
Linux, the derived-work question comes in to play.)

On Sat, 6 Nov 2004 02:40:35 -0800, Adam J. Richter <adam@yggdrasil.com> wrote:
> >  == David Schwartz
> >> == Jerome Petozzoni
> >> Can Broadcom and the vendors "escape" the obligations of the GPL by
> >> shipping those proprietary drivers as modules, or are they violating the
> >> GPL plain and simple by removing the related source code (and showing
> >> irrelevant code to show "proof of good will") ?
> >
> >        That is a contentious issue that has been debated on this group far too
> >much. In the United States, at least, the answer comes down to the complex
> >legal question of whether the module is a "derived work" of the Linux kernel
> >and whether the kernel as shipped with those modules is a "mere
> >aggregation".
>         I think you're missing the idea that that such drivers are
> _contributory_ infringement to the direct infringement that occurs when
> the user loads the module.  In other words, even for a driver that has
> not a byte of code derived from the kernel, if all its uses involve it
> being loaded into a GPL'ed kernel to form an infringing derivative
> work in RAM by the user committing direct copyright infringement against
> numerous GPL'ed kernel components, then it fails the test of having
> a substantial non-infringing use, as established in the Betamax decision,
> and distributing it is contributory infringement of those GPL'ed
> components of the kernel.

-- 
Disconnect <dc.disconnect@gmail.com>
http://www.gotontheinter.net/

  parent reply	other threads:[~2004-11-05 18:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-06 10:40 Possible GPL infringement in Broadcom-based routers Adam J. Richter
2004-11-05 18:51 ` Michael Poole
2004-11-05 18:58 ` Disconnect [this message]
2004-11-05 19:03 ` David Schwartz
2004-11-05 19:38   ` linux-os
2004-11-05 19:06 ` Horst von Brand
2004-11-05 19:39   ` Arjan van de Ven
2004-11-06  3:21   ` Kyle Moffett
  -- strict thread matches above, loose matches on Subject: below --
2004-11-05 18:43 Adam J. Richter
2004-11-05 19:59 ` David Schwartz
2004-11-06  3:23   ` David Woodhouse
2004-11-06 20:09     ` David Schwartz
2004-11-06 21:40       ` Stephen Pollei
2004-11-07 17:05       ` David Woodhouse
2004-11-06 13:38 ` Horst von Brand
2004-11-06 15:49   ` Arjan van de Ven
2004-11-07 21:08     ` Ryan Anderson
2004-11-05 18:31 Adam J. Richter
2004-11-05 18:20 Adam J. Richter
2004-11-05 20:00 ` Michael Poole
2004-11-04 23:33 Jérôme Petazzoni
2004-11-04 23:57 ` David Schwartz
2004-11-05  0:23   ` Kyle Moffett
2004-11-05 15:27   ` David Woodhouse
2004-11-05  4:05 ` Scott Lockwood
2004-11-05 20:28 ` Tonnerre

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=55f6199c041105105861a25172@mail.gmail.com \
    --to=dc.disconnect@gmail.com \
    --cc=adam@yggdrasil.com \
    --cc=jp@enix.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