Simon,
Thanks ! I fact I though 0 means don't wait at all.
Huh...usually 0 means don't wait and (-1) means wait forever. As I
understand you, here is all the opposite. Is this the same for mailboxes ?
I was sure it was just a "formal" problem from my side !
Thanks again,
marko
[EMAIL PROTECTED] wrote:
Marko Panger wrote:
1) netconn_new_with_proto_and_callback() creates the semaphore and
the semaphore is initialized to 0. After that tcpip_apimsg() is
invoked which sends the do_newconn() function to the main tcp thread.
The tcpip_apimsg() function pends on the op_completed semaphore with
0 time.
Just to ensure you get this right: '0' means infinite, not 'test and
return' -> the app task should wait for the tcpip_thread to complete
the function request.
Simon
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users
__________ NOD32 2811 (20080121) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users
