Chuck Kuecker wrote:
No, the LWIP timers are called from the main timer tick, and there are
no other threads. This is how LWIP is set up for the Luminary driver
library I am using, and it has always worked before.
So lwIP is running in the main thread and the timers are called from
intterupt level?? If so, the people creating the port have done
something wrong (unless they set up some own protected against
concurrent access). The main principle is that the core of lwIP is *not*
protected against concurrent access which is why all functions may only
be called from one thread and not from interrupt context (except for
some memory allocation functions and the API functions).
Wireshark shows no defective packets.
That's good to know. You could still check the stats (or enable debug
output) to see if there's something going wrong inside the stack.
Simon
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users
