All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Florian Schirmer <jolt@tuxbox.org>
Cc: linux-kernel@vger.kernel.org, David Turner <novalis@fsf.org>,
	andrew@mikl.as, rob@nocat.net
Subject: Re: Linksys/Cisco GPL Violations
Date: Fri, 10 Oct 2003 14:39:04 +0100	[thread overview]
Message-ID: <1065793144.24015.274.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <023501c38f32$2b83caa0$9602010a@jingle>

On Fri, 2003-10-10 at 15:26 +0200, Florian Schirmer wrote:
> The ethernet and wireless driver where never linked into the kernel.
>  So it should be okay if they only distribute the module.

That is true, according to the GPL, _only_ if the modules are
distributed as separate works. If they are part of a collective work
which is based on the kernel (note, not a _derived_ work but a
_collective_ work) then they must be released under the terms of the
GPL.

This is a _different_ issue to the question of whether a module is
indeed a derived work, and it's _far_ more clear-cut.

Ask yourself the following questions:

1. The wireless and Ethernet driver modules are distributed within
   a cramfs file system in a flash image on a chip soldered to the
   board of the device.

   Are they being distributed 'as separate works'?

2. The fundamental mode of operation of these devices is to
   receive network packets from one of the drivers, pass them
   through the Linux kernel routing or bridging code, and then
   back out through another of the network interfaces. All 
   three parts of this are indispensable and the product is 
   useless without any one part.

   A) Does this form a whole which is a derived work based on the
      Linux kernel?

   B) Does this form a whole which is a collective work?

   C) Is this collective work based, in part, on the Linux kernel?

3. Refer back to the facts in question 1. Is this 'mere aggregation
   of a work not based on the [kernel] on a volume of a storage or
   distribution medium'?

Now, having answered those questions, reread the final three paragraphs
of §2 of the GPL.

-- 
dwmw2


  reply	other threads:[~2003-10-10 13:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 18:22 Linksys/Cisco GPL Violations David Turner
2003-10-06  8:29 ` David Woodhouse
2003-10-10 13:09   ` Florian Schirmer
2003-10-10 13:16     ` David Woodhouse
2003-10-10 13:26       ` Florian Schirmer
2003-10-10 13:39         ` David Woodhouse [this message]
2003-10-10 14:18           ` Florian Schirmer
2003-10-10 14:25             ` David Woodhouse
2003-10-11  5:37               ` Andre Hedrick
2003-10-11  6:35                 ` David Woodhouse
2003-10-11  7:03                   ` Andre Hedrick
2003-10-13  9:40                   ` Florian Schirmer
2003-10-10 15:11     ` [Linux-bcom4301-priv] " James Stevenson
2003-10-10 15:29       ` Sasa Ostrouska
2003-10-10 16:36         ` Florian Schirmer
2003-10-10 16:58           ` Luite Stegeman
2003-10-10 15:58     ` Rob Flickenger

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=1065793144.24015.274.camel@hades.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=andrew@mikl.as \
    --cc=jolt@tuxbox.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=novalis@fsf.org \
    --cc=rob@nocat.net \
    /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.