Maybe a simple way to access lwIP functions in a safe way is to use core locking mode (LWIP_TCPIP_CORE_LOCKING). Acquire lwIP core lock (LOCK_TCPIP_CORE() / UNLOCK_TCPIP_CORE()) before you perform operations on any lwIP structure or call to lwIP functions.
I just saw these functions are in tcpip_priv.h - they should be moved to tcpip.h. Note you need a good mutex implementation for that (priority inversion safe). Dirk -- Dirk Ziegelmeier * [email protected] * http://www.ziegelmeier.net On Fri, Apr 22, 2016 at 6:23 PM, Sergio R. Caprile <[email protected]> wrote: > RAW API functions must be called in the same thread as the lwIP core > functions. In fact, afaik, except for netconn and socket API, all lwIP > functions must be called from the same thread. > You can run RAW API apps on the lwIP thread, and netconn/socket API apps > on other threads. > There is a running web server in the contrib tree for the RAW API. > There is a (somehow) enhanced web server for the RAW API on my website ( > http://scaprile.ldir.com.ar/cms/el-ingeniero/open-source-projects-im-working-on/lwhttpd/ > ) > I can't help you with netconn. > If you need help on writing your own app for the netconn API, open a new > thread, explain that in the subject, and wait for someone to drop in. > > > > > _______________________________________________ > lwip-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/lwip-users >
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
