All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Poole <mdpoole@troilus.org>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: davids@webmaster.com, jp@enix.org, linux-kernel@vger.kernel.org
Subject: Re: Possible GPL infringement in Broadcom-based routers
Date: 05 Nov 2004 13:51:57 -0500	[thread overview]
Message-ID: <87oeicuo1e.fsf@sanosuke.troilus.org> (raw)
In-Reply-To: <200411061040.iA6AeZp03452@freya.yggdrasil.com>

Adam J. Richter writes:

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

Combining GPLed works with GPL-incompatible works violates the GPL if
you distribute the result; the GPL allows one to make that kind of
combination for one's own use.  Go read the GPL more closely.

Michael Poole

  reply	other threads:[~2004-11-05 18:52 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 [this message]
2004-11-05 18:58 ` Disconnect
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=87oeicuo1e.fsf@sanosuke.troilus.org \
    --to=mdpoole@troilus.org \
    --cc=adam@yggdrasil.com \
    --cc=davids@webmaster.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.