From: "Florian Schirmer" <jolt@tuxbox.org>
To: "David Woodhouse" <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 15:26:53 +0200 [thread overview]
Message-ID: <023501c38f32$2b83caa0$9602010a@jingle> (raw)
In-Reply-To: 1065791790.24015.238.camel@hades.cambridge.redhat.com
Hi,
> I just built the kernel for the WAP54G (wap54g.1.08.tar.gz) and it seems
> to contain only object code for the wireless driver.
>
> In which version did you find the source?
The ethernet and wireless driver where never linked into the kernel. So it
should be okay if they only distribute the module. They decided to provide
object code. Which is far better than a linked the module. I'm aware of the
current discussion wether binary modules are legal or not. The main Linksys
case was about the GPL violation by linking stuff into the kernel. _That_ is
resolved now. The wireless driver is a completely different story. IMHO.
Regards,
Florian
next prev parent reply other threads:[~2003-10-10 13:26 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 [this message]
2003-10-10 13:39 ` David Woodhouse
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='023501c38f32$2b83caa0$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox