You're right, netconn API and socket API need NO_SYS=0
----- Original Message -----
From: Bill Auerbach
To: 'Mailing list for lwIP users'
Sent: Wednesday, January 02, 2008 10:05 PM
Subject: [lwip-users] Is the API functional with NO_SYS=1?
Hello group - Happy New Year!
I'm still going down the path of using NO_SYS=1 in my application, but I'm
beginning to think because I'm in apparently less-traveled territory here that
this may turn out to be a bad idea.
The question is, are the APIs functional with NO_SYS=1? netconn_accept
doesn't block and so I wonder if this is wrong or if the APIs aren't meant for
no OS. I can run in a loop calling functions as needed, based on their timeout
intervals, and DHCP finds an IP address and then I can Ping successfully. So
lwIP is otherwise functional as I've implemented it with NO_SYS=1.
If NO_SYS=1 isn't a good idea, what can be done for a minimal lwIP single
threaded application to emulate an OS? I now can periodically call the lwIP
timing functions (tcp_tmr, arp_timer, ip_reass_tmr, dhcp_fine_tmr, and
dhcp_coarse_tmr) as needed watching an mS free running counter.
Thank you,
Bill Auerbach
------------------------------------------------------------------------------
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users
