This is the mail archive of the
mailing list for the eCos project.
ecos + lwip
- From: Mandeep Sandhu <mandeepsandhu dot chd at gmail dot com>
- To: ecos-discuss <ecos-discuss at ecos dot sourceware dot org>
- Date: Wed, 26 Aug 2009 16:31:25 +0530
- Subject: [ECOS] ecos + lwip
I'm writing my app which makes use of the lwIP stack to send/recv packets.
I'm using lwIP that comes along with ecos-3.0 (which I think is ver 1.1.1).
I started by looking at the "test" examples given with lwIP. I noticed
that ALL examples
create 2 threads. One which simply starts and calls the following
functions and exits:
The thread started as part of sys_thread_new does the main
functionality of the app.
>From the source I saw that sys_thread_new() simply allocates resources necessary
for starting the lwIP stack and then schedules the user function for execution.
* Does the lwIP stack run within the context of the thread started by
* If my app has to start 2 threads, both creating separate sockets and
send/recv data over
it, then should only one of them be created with a call to
sys_thread_new()? While the other
one is started by our regular cyg_thread_create() and friends?
Sorry if this is a dumb question.
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss