lwip-contrib-mac/ports/ecos
2003-07-29 14:52:12 +00:00
..
ecos Fix compilation for PPP and for the case when net_drivers package is not added. Initialize loopif, prevent lwip_init being run more than once and fix lwip_set_addr to not chop off the netif_list.All these in init.c for ecos 2003-07-29 14:52:12 +00:00
copy Add eCos glue. 2003-02-28 14:29:13 +00:00
files Add loopif to the ecos port too 2003-07-29 14:48:59 +00:00
ioeth.diff Changed DEBUGF to LWIP_DEBUGF 2003-06-10 10:45:29 +00:00
mkepk make test not bash specific 2003-05-05 14:56:27 +00:00
README add patch against ecos needed for the glue to wotk 2003-03-01 10:47:38 +00:00

This part of the lwip-contrib section is the ecos glue  

Check out latest ecos or beta 2 if available and apply ioeth.diff to packages/io/eth

You must have the current lwip sources checked out and the scripts here will hopefully generate
a correct EPK suitable for use with ecos.


To make an ecos package:

Run the mkepk script something like this

# EPK=/dir/of/epk LWIP_CVS=/dir/of/checked/out/lwip ./mkepk

This will put the generated EPK in the dir you specify


then add that EPK to your package repository and use it

Build example:
#ecosconfig new edb7xxx kernel
#ecosconfig add lwip
this will default to SLIP connection.If you also
#ecosconfig add net_drivers
you'll be able to configure for ethernet

In both cases set LWIP_MY_ADDR and LWIP_SERV_ADDR (means host/gateway for eth or host/peer for slip)
#ecosconfig tree
#make tests
and you can try any of the five tests included

Tests:
udpecho - echo service port 7 on UDP
tcpecho - ditto on TCP
sockets - as tcpecho but written with the socket API not the lwip specific API
https - http server on port 80 written with the raw API
nc_test_slave - a port of the test with the same name in net/common to lwip. Used to compare 
		lwIP throughput to that of the FreeBSD stack.In this matchup lwIP gets a well deserved 
		silver medal.Not bad for a newcomer ;)
		

Bugreports (or even better patches) at jani@iv.ro not the lwip or ecos mailing lists!!
Only if you peek into the lwip sources and think you found a bug post to lwip-users.