All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Florian Schirmer" <jolt@tuxbox.org>
To: <dwmw2@infradead.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 16:18:58 +0200	[thread overview]
Message-ID: <02b001c38f39$72baabd0$9602010a@jingle> (raw)
In-Reply-To: 1065793144.24015.274.camel@hades.cambridge.redhat.com

Hi,

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

Dont get me wrong. I agreee that there are still issues with the wireless
driver. IMHO binary modules aren't legal at all. I just don't wanted to
start the binary discussion and therefore posted the misleading statement.

Regards,
   Florian


  reply	other threads:[~2003-10-10 14:19 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
2003-10-10 14:18           ` Florian Schirmer [this message]
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='02b001c38f39$72baabd0$9602010a@jingle' \
    --to=jolt@tuxbox.org \
    --cc=andrew@mikl.as \
    --cc=dwmw2@infradead.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.