From: Simon Kallweit <simon.kallweit@intefo.ch>
To: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] lwIP 1.3 port
Date: Mon, 08 Dec 2008 18:00:00 -0000 [thread overview]
Message-ID: <493D4B8D.9070309@intefo.ch> (raw)
In-Reply-To: <493D2264.2050204@intefo.ch>
>
> Single-threaded operation:
>
> In this mode, a single thread is used for all handling of the stack.
> In the current port, the user needs to initialize lwIP "by hand",
> setup timeouts etc. I would like to write some glue code to simplify
> usage of lwIP in this mode. The glue code should implement an
> initialization routine as well as the basic operation of the lwip
> thread (similar to what the tcpip thread in the threaded version
> provides). Basic timeouts of the protocols should automatically be
> handled when enabled in the configuration, and ethernet drivers should
> be polled. I would also like to integrate SLIP and PPP support. As
> these have to run in a separate thread (for serial communication), we
> need a simple queue to pass received packets to the main thread.
After some more thought, the single thread implementation does not seem
to be that easy. The main reason is that I need SLIP and PPP, not
necessarily ethernet. The current lwIP implementation of PPP and SLIP
depend on multiple threads though. SLIP does blocking reads on the
serial device and PPP requires the sys_timeouts from lwIP for timeout
handling. I guess they can be adapted for single threaded operation, but
not without touching the lwIP code obviously.
The SLIP code would have to be changed to non-blocking operation. This
is rather simple. Porting PPP to single thread usage is rather a bit
tricky though, but I still manageable. My current plan is to do the SLIP
changes first, see how it works and then continue with PPP.
Is there anyone interested in testing or helping out?
Simon
--
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:[~2008-12-08 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 16:30 Simon Kallweit
2008-12-08 18:00 ` Simon Kallweit [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=493D4B8D.9070309@intefo.ch \
--to=simon.kallweit@intefo.ch \
--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).