From: Andrew Lunn <andrew@lunn.ch>
To: Andrea Merello <andrea.merello@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] GPL violation ?
Date: Thu, 30 Aug 2007 14:28:00 -0000 [thread overview]
Message-ID: <20070830142837.GQ31057@lunn.ch> (raw)
In-Reply-To: <c68f135e0708300452p32f0009ax56497956c1cfb184@mail.gmail.com>
> 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
I disassembled the startup code and compared it to the
arm/arch/current/src/vectors.S. It looks like it is a RAM startup
eCos image.
As another poster pointed out, the exception to the GPL means that you
can only ask for the eCos sources and any code derived from the eCos
sources, eg there HAL packages, probably there serial port driver,
flash driver, etc.
It is unlikely they have used eCos code when writing there
"application" code, ie what actually drives the WLAN MAC. So it is
unlikely you can get that code.
So if you want to run "hello world" on there WLAN hardware, you
shouldn't have a problem.
If you want to write your own firmware to drive the WLAN hardware they
can at least get a basic working eCos as a foundation for you to write
your own firmware for the WLAN hardware.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-08-30 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 11:52 Andrea Merello
2007-08-30 13:51 ` Mike Arthur
2007-08-30 14:28 ` Andrew Lunn [this message]
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=20070830142837.GQ31057@lunn.ch \
--to=andrew@lunn.ch \
--cc=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).