Lines Matching full:can
28 * All APIs can be used simultaneously by different application
50 * closed, etc. An application can provide a callback function to perform
65 * Sequential-style APIs, blocking functions. More overhead, but can be called
78 * Can be activated by defining @ref LWIP_SOCKET to 1.\n
135 * lwIP can be used in two basic modes: @ref lwip_nosys (no OS/RTOS
143 * In mainloop mode, only @ref callbackstyle_api can be used.
164 * In OS mode, @ref callbackstyle_api AND @ref sequential_api can be used.
175 * 1) tcpip_callback() can be used get called back from TCPIP thread,
179 * functions can be called when lwIP core lock is aquired, see
225 * *not* *from* *interrupt* *context*. You can allocate a @ref pbuf in interrupt
230 * You can only use @ref callbackstyle_api in this mode.\n
242 * You can use @ref callbackstyle_api together with @ref tcpip_callback,
252 We can give you some idea on how to proceed when using the raw API.
301 You can peek in the netif->dhcp struct for the actual DHCP status.
373 routine from src/core/inet.c. You can override this standard
380 Other significant improvements can be made by supplying