From: "Andrea Merello" <andrea.merello@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] GPL violation ?
Date: Thu, 30 Aug 2007 11:52:00 -0000 [thread overview]
Message-ID: <c68f135e0708300452p32f0009ax56497956c1cfb184@mail.gmail.com> (raw)
Hi!
It happened I found a device that I suspect uses eCos OS in firmware,
but I can't get source from the vendor site. So I suspect they are
violating GPL and would like to investigate. I have not contacted the
vendor yet directly, I'd like to know if they are really usign eCos
and if they eventually had been authorized by eCos developer before go
on..
The device is a PCI wireless card from Marvell
Ethernet controller: Marvell Technology Group Ltd. 88w8335 [Libertas]
802.11b/g Wireless (rev 03).
It has and ARM processor where the firmare runs..
I'm developing a driver for it, on Linux OS, to properly initialize
the device, the driver has to upload the firmware in the device RAM.
The firmware I used is from the BSD package.
You can find it here
http://www.nazgul.ch/malo/malo-firmware-1.0.tgz
Iit looks like it is the same firmware that is contained in the
windows driver officially distributed with the card.
The windows firmware can be obtained using the utility here
http://www.saillard.org/linux/mrv8k/files/mrv8k_extract_fw.c
I suspect this firmware is based on eCos because
daiquiri:/home/user # strings /usr/lib/hotplug/firmware
/mrv8k- f.fw |grep -i ecos
eCos :
ARM eCos
daiquiri:/home/user #
Thank you
Andrea
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2007-08-30 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 11:52 Andrea Merello [this message]
2007-08-30 13:51 ` Mike Arthur
2007-08-30 14:28 ` Andrew Lunn
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=c68f135e0708300452p32f0009ax56497956c1cfb184@mail.gmail.com \
--to=andrea.merello@gmail.com \
--cc=ecos-discuss@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).