This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Including TCP/IP stack in an eCos application.

From: "David Ho" <davidkwho at gmail dot com>
To: "Andrew Lunn" <andrew at lunn dot ch>, "eCos discuss list" <ecos-discuss at ecos dot sourceware dot org>
Date: Tue, 8 Aug 2006 10:09:06 -0400
Subject: Re: [ECOS] Including TCP/IP stack in an eCos application.
References: <4dd15d180608080637r366505b7p90acfa3c7822eb4f@mail.gmail.com> <20060808134506.GC19600@lunn.ch>

On 8/8/06, Andrew Lunn <andrew@lunn.ch> wrote:

This is probably not a good comparison. I expect the linker has been
able to throw away a lot of lwip and not much of FreeBSD. So when you
start writing an application, the lwip size will increase much faster
than the FreeBSD size.

From our experience, we have a working LWIP stack running without an

OS and running with FreeRTOS on the same target.  The actual memory
usage for running a simple web server is around 10KB text.  So it is
still a much better alternative than Net/FreeBSD at this moment.

David

PS Your reply-to: address in this email seems to point back to me for
some reason?

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

References:
- Including TCP/IP stack in an eCos application.
  - From: David Ho
- Re: Including TCP/IP stack in an eCos application.
  - From: Andrew Lunn

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]