[ECOS] Starting new eCos project
James Graves
james.graves@deltamobile.com
Tue Oct 28 01:40:00 GMT 2008
Andrew Lunn wrote:
>> For a follow-on project to this one which will also be using this
>> platform, we'll need TCP/IP networking. The network driver will be
>> written by us (or maybe adapted from Linux). Looks like we should be
>> using the FreeBSD stack, based on a little digging in this mailing list.
>
> Be careful with Linux kernel code. It is GPL, where as eCos is a
> modified GPL. If you use pure GPL code, your whole system becomes GPL
> and then you need to do things like make all your source code
> available to your customer.
That's a good point. We may have to write our own driver instead.
> Another thing to watch out for is that the sourceware ARM toolchain is
> broken when used with jffs2. You need to use a newer version. If you
> try to use the broken one you will get a #error when compiling.
Thanks for the tip. I was looking at the toolchain building
instructions, and also saw this discussion:
http://sourceware.org/ml/ecos-discuss/2008-09/msg00040.html
So I guess I'll try to use the CodeSourcery 2008q3-39 ARM EABI, and
compile the latest newlib (v1.16.0) and GDB with that. Should be fun.
I'll make a point to keep some notes on the process, and post anything
useful to the list.
Best regards,
James
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
More information about the Ecos-discuss
mailing list