Re: lwip 1.3.1 testing

[John Dallaway <john@dallaway.org.uk>]

Hi Simon

Simon Kallweit wrote:

>> The lwIP CDL script currently builds ecos/sio.c unconditionally so
>> CYGPKG_IO_SERIAL is required even when both PPP and SLIP are disabled.
>> It would be good to compile ecos/sio.c via a CDL option which is
>> "calculated { CYGPKG_LWIP_PPP || CYGPKG_LWIP_SLIP }" if other source
>> code will permit this.
> 
> sio.c is always compiled, but there is an #ifdef which includes the code
> only when either CYGPKG_LWIP_SLIP or CYGFUN_LWIP_PPPOS_SUPPORT is
> active. Also, CYGPKG_IO_SERIAL_DEVICES is only enabled if either SLIP or
> PPPoS support is enabled. Do you think solving that dependency in CDL is
> the better approach?

OK, it seems that this issue has already been resolved. I was looking at
a slightly older revision of sio.c. As a general rule, it's preferable
to compile only those source code files which are needed. Clearly the
most important thing is to ensure that the resulting binaries are not
bloated with unused code/data.

>> How is you own testing of lwIP 1.3.1 progressing?
> 
> Well, I'm currently using devices with lwIP 1.3.1 in field tests. They
> run in the 'simple' mode (single-threaded) and use PPP for GPRS
> connections via a GSM modem. I have not seen any issues with the current
> port. The devices run for days until they may be power-cycled for
> updates or maintenance.
> 
> Application development is done on the synthetic target, using a
> simulated GSM modem, simulating GPRS connections by spawning a local PPP
> server. No issues have occurred with this configuration either, although
> runtimes are usually only minutes to hours.

So I think we should roll this out to eCos CVS soon. This will help with
further testing coverage.

One minor point: It would be very useful for the stack to report its own
IP address on the diagnostic channel.

John Dallaway