[RTEMS Project] #3850: Modular Network Stacks

[RTEMS trac]

#3850: Modular Network Stacks
--------------------------+--------------------------
 Reporter:  Gedare Bloom  |       Owner:  Chris Johns
     Type:  project       |      Status:  assigned
 Priority:  normal        |   Milestone:  Indefinite
Component:  admin         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  SoC,kernel    |  Blocked By:
 Blocking:                |
--------------------------+--------------------------

Comment (by Gedare Bloom):

 From Joel on the users mailing list:

 One thing to be aware of is that all the POSIX networking header files for
 RTEMS are in newlib and always present. I had to address this and lwip
 when we did Deos+RTEMS. Deos uses lwip as their native stack running in a
 partition and other partitions use a client to get to it. The lwip
 constants had values that were not the same as the RTEMS BSD headers for
 POSIX defines. There were also some places where the structure definitions
 did not align. I had to write a bit of mapping in the client. When lwip
 works at all, it would be awesome to have a way for it to ignore their own
 minimal POSIX API files and build against ours.

 This would be similar to how the newlib headers define a very complete
 POSIX API set but each target OS may only support a subset of it.

 As it is, I wonder if there is a conflict between the RTEMS newlib network
 .h files and those provided by lwip which could cause issues.

--
Ticket URL: <http://devel.rtems.org/ticket/3850#comment:2>
RTEMS Project <http://www.rtems.org/>
RTEMS Project