[lwip-users] Re: [lwip] lwIP in a non-OS environment

[Alexander Groß]

Hi Paul,

the problem is that I am not able to implement the operating system into my
network layer. I have to build a network layer (library) that can be linked
against *any* of our projects. All our projects do not support operating
systems and therefore it is not acceptable to change any line of source code
to add TCP/IP functionality to the project. The network API we use is a
company-wide standard and there are already implementations for RS-232 and
CANopen (a fieldbus with application layer).

The TCP/IP-based solution should be able to replace any other network layer
just by selecting another network lib without making changes to the source
code of the application.

Best regards,

Alex
----- Original Message -----
From: "Paul Sheer" <address@hidden>
To: <address@hidden>; "Carsten Thomas" <address@hidden>; "Adam
Dunkels" <address@hidden>; <address@hidden>
Sent: Wednesday, February 13, 2002 8:29 AM
Subject: Re: [lwip] lwIP in a non-OS environment


|
| I have the EXACT answer to your question
|
| I am developing an OS, called PaulOS that filfulls all
| of your requirements.
|
| - it operates in a single thread
| - it employs NO locking whatsoever
| - it has a minimal POSIX layer for convenience
| - it runs on the ARM7TDMI
| - it is written entirely in C with only 2 or 3
| architecture specific files
| - it currently runs lwIP during the idle
| cycles of any POSIX call where the POSIX
| call blocks waiting for an event or
| timeout.
| - it does not use interrupts except where
| absolutely necessary
|
| On the ARM, the entire image is 90kB, which includes
| a minimal termios layer, web server and ARM serial
| driver.
|
| Do you want to create a port for your processor?
|
| best
|
| -paul


[This message was sent through the lwip discussion list.]