From: Harald Welte <laforge@gpl-violations.org>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: APs from the Kernel Summit run Linux
Date: Tue, 30 Aug 2005 14:56:49 +0200 [thread overview]
Message-ID: <20050830125648.GG4295@rama.de.gnumonks.org> (raw)
In-Reply-To: <20050830121810.GA11582@midnight.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 2579 bytes --]
On Tue, Aug 30, 2005 at 02:18:10PM +0200, Vojtech Pavlik wrote:
> > If it is from the ASUS, what makes you think that the D-Link runs the
> > same OS? It is quite often the case that one chipset design has
> > multiple operating systems ported to it (you see systems with the same
> > broadcom or Intersil chipset, one running Linux, the other VxWorks).
>
> > Please indicate how you came to the conclusion that the D-Link really
> > runs Linux.
>
> The device's ESSID during boot is 'Marvell AP-32', and the Libertas
> AP-32 and AP-52 design toolkits contain only ports of Linux and eCos to
> the device, according to Marvell. Considering the device's routing
> capabilities I'm believe it's running Linux, but I don't have a solid
> proof yet, unfortunately. The eCos port is intended for the non-router
> variety of the design.
There could also be a 3rd party toolkit with a different OS that you
don't know about...
> On the other hand, eCos seems to be GPL, too, although it's possible
> that the owner dual-licenses it.
According to http://sources.redhat.com/ecos/, it is either still RedHat
or already transferred to the FSF. That doesn't sound like dual
licensing, I don't think the FSF would do that...
> > > A firmware image is available from D-Link
> > > and it seems to be composed of compressed blocks padded by zeroes. I haven't
> > > verified yet that it's indeed a compressed kernel, cramfs, etc, but it seems
> > > quite likely.
> >
> > I'm downloading it right now, and I'll see whether I can find any Linux
> > in there.
>
> Good luck. I'll try to take a look, too.
Up to now I can only tell you that it doesn't look like any of the 50+
linux firmware images I've seen so far.
> > Sure, it's (unfortunately) not the first time I'm dealing with D-Link on
> > their GPL [in]compliance :((
>
> Rather unrelated, I'm trying to figure out what to do with Elo
> Touchsystems, they used my HID driver as a base of their own binary-only
> driver and don't answer to e-mail.
Well, if you seriously want to do something about it: They have a German
subsidiary. So if the respective product can be bought through that .de
office, we can do something about it here. Let's take this offline.
--
- Harald Welte <laforge@gpl-violations.org> http://gpl-violations.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-30 13:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050830085522.GA8820@midnight.suse.cz>
2005-08-30 10:19 ` Harald Welte
2005-08-30 12:18 ` Vojtech Pavlik
2005-08-30 12:56 ` Harald Welte [this message]
2005-08-30 13:12 ` Vojtech Pavlik
2005-08-30 14:30 ` Alan Cox
2005-08-30 20:17 ` David Lang
2005-08-30 9:37 Vojtech Pavlik
2005-08-30 15:49 ` Michael Tokarev
2005-08-30 16:01 ` Vojtech Pavlik
2005-08-31 16:55 ` Mark Lord
2005-08-31 17:02 ` Vojtech Pavlik
2005-08-31 19:53 ` Russell King
2005-08-31 20:32 ` Vojtech Pavlik
2005-08-31 20:50 ` Mark Lord
2005-09-01 3:29 ` Kyle Moffett
2005-09-01 3:36 ` Nigel Cunningham
2005-09-01 15:39 ` Pavel Machek
2005-09-01 21:50 ` Vojtech Pavlik
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=20050830125648.GG4295@rama.de.gnumonks.org \
--to=laforge@gpl-violations.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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®