From: "Jérôme Petazzoni" <jp@enix.org>
To: linux-kernel@vger.kernel.org
Subject: Possible GPL infringement in Broadcom-based routers
Date: Fri, 05 Nov 2004 00:33:51 +0100 [thread overview]
Message-ID: <418ABC5F.6060200@enix.org> (raw)
The following routers (and they might be other models, too) :
- Us Robotics 9105 (without wireless) and 9106 (with wireless)
- Siemens SE515
- Dynalink RTA230
- Buffalo WMR-G54
- Inventel DBW-200
... are all based on the same Broadcom chipset (96345 board). They
integrate a 4-ports Ethernet switch, a 802.11g wireless access point,
and a DSL modem (and doing routing and/or bridging between those
interfaces). The CPU runs the MIPS32 instruction set. It runs a 2.4.17
linux-mips kernel with additional patches, and is loaded with a lot of
free software (busybox, uclibc, zebra...)
The vendors (probably Broadcom, in fact) had to patch the kernel to
support the DSL modem, the wireless interface (which is a PCMCIA-hosted
BCM4306 ; which already was subject of heated debates earlier), and also
some generic stuff like the flash memory and the front leds.
Miscellaneous vendors provide so-called "GPL sources", which are
generally mutilated kernels, lacking all the "interesting" parts
(wireless and DSL drivers for instance).
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") ?
Broadcom has been contacted about this matter but hasn't answered so
far, nor did US Robotics (I tried to contact USR since I own a USR router).
Any suggestions about the legal (or if it's a lost cause, technical!)
ways to get support for this platform will be very welcome.
More information can be found here :
http://skaya.enix.org/wiki/GplInfringement (some extra details)
http://skaya.enix.org/wiki/BroadCom96345 (technical info that I gathered
about the router, firmware and kernel formats, etc.)
http://sourceforge.net/projects/brcm6345-linux/ (sourceforge project)
Best regards,
Jérôme Petazzoni <jp at enix dot org>
PS: please be kind and cc me, as my lkml awareness is limited to KT ...
next reply other threads:[~2004-11-04 23:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 23:33 Jérôme Petazzoni [this message]
2004-11-04 23:57 ` Possible GPL infringement in Broadcom-based routers 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
-- strict thread matches above, loose matches on Subject: below --
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=418ABC5F.6060200@enix.org \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox