mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: davids@webmaster.com
Cc: linux-kernel@vger.kernel.org
Subject: RE: Possible GPL infringement in Broadcom-based routers
Date: Fri, 05 Nov 2004 15:27:49 +0000	[thread overview]
Message-ID: <1099668469.4542.36.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKCENFPIAA.davids@webmaster.com>

On Thu, 2004-11-04 at 15:57 -0800, David Schwartz wrote:
> > 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".

Not quite.

It comes down to a question of whether their firmware as a whole is a
'collective work' based in part on the Linux kernel, or whether the
whole thing can be considered 'mere aggregation' despite the fundamental
interdependency between the kernel and their drivers, without either of
which the entire device would be useless.

	"These requirements apply to the modified work as a whole.  If
	identifiable sections of that work are not derived from the
	Program, and can be reasonably considered independent and
	separate works in themselves, then this License, and its terms,
	do not apply to those sections when you distribute them as
	separate works."

This is the bit you seem to be thinking of -- when it's not actually a
derived work. But the GPL goes on and explicitly talks about your
obligations with respect even to non-derived works, if distributed as
part of a larger whole:

		        "But when you distribute the same sections as
	part of a whole which is a work based on the Program, the
	distribution of the whole must be on the terms of this License,
	whose permissions for other licensees extend to the entire
	whole, and thus to each and every part regardless of who wrote
	it.
                                                                                	"Thus, it is not the intent of this section to claim rights or
	contest your rights to work written entirely by you; rather, the
	intent is to exercise the right to control the distribution of
	derivative or collective works based on the Program."


-- 
dwmw2


  parent reply	other threads:[~2004-11-05 15:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2004-11-05  4:05 ` Scott Lockwood
2004-11-05 20:28 ` Tonnerre
2004-11-05 18:20 Adam J. Richter
2004-11-05 20:00 ` Michael Poole
2004-11-05 18:31 Adam J. Richter
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-06 10:40 Adam J. Richter
2004-11-05 18:51 ` Michael Poole
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

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=1099668469.4542.36.camel@hades.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=davids@webmaster.com \
    --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®