[ECOS] Linux or ecos?

Gary Thomas gthomas@redhat.com
Wed Nov 7 07:23:00 GMT 2001

On Thu, 2001-11-15 at 01:59, Roland Caßebohm wrote:
> Andrew Lunn wrote:
> > 
> > The TCP/IP stack can eat of lot of DRAM. How fast a network link do
> > you need. You can trade off speed for network buffer speed.
> > 
> > The ethernet device you use will also have a big affect. eg the i82559
> > uses 1Mbyte of RAM for its PCI window. I don't expect you will use
> > this device because its expensive and requires a PCI bridge etc. A
> > simpler, slower device with polled IO will require less memory, but
> > perform much slower.
> > 
> > If you application is really simple, you could think about building it
> > into redboot itself. That has its own really simple IP stack and basic
> > drivers for the serial ports.
> > 
> >         Andrew
> The i386 hardware have an ne2000 compatible chip on it and the arm and
> mips hardware I down't by now. I think it will be onchip.
> There is another idea I think of, I want to write source of my
> application POSIX compatible because in future the application will be
> more complex, so that I have to use Linux then. But in the release of
> ecos which I have downloaded (1.3.1) I haven't seen POSIX funktions. 

You need to get the anonymous CVS version of eCos to get the POSIX 
functionality.  Indeed, you'll need anonCVS to get RedBoot as well.

> I have read the documentation of building redboot. Is it right that
> redboot is a simple ecos with a simple application?

Yes, RedBoot is just an eCos application which happens to use only
a [small] portion of the eCos HAL - no kernel, no threads.

More information about the Ecos-discuss mailing list