> You are right. A had a quick look into the timer function 
> calls in api/tcpip.c and they get called way to fast. What 
> can be the case for that? In sys_arch_timeouts() I return a 

Maybe you have one of those ports that don't return the correct
value how long they waited for a semaphore/message. sys_arch_mbox_fetch
and sys_arch_sem_wait should return the time in milliseconds waited
for a message. E.g. if they didn't have to wait because a message was
available, 0 should be returned.
This is one limitation of the current timeout implementation!


Simon


_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users

Reply via email to