Lines Matching full:when

14 the various protocols. It is the only API available when running lwIP
33 lwIP started targeting single-threaded environments. When adding multi-
36 (also known as the "tcpip_thread"). When running in a multithreaded
105 invoked by the lwIP core when activity related to that application
152   Commands a pcb to start listening for incoming connections. When an
178   Specified the callback function that should be called when a new
192   when the connection is established. If the connection could not be
206 tcp_write(). When the data is successfully transmitted to the remote
239   Specifies the callback function that should be called when data has
248 callback function is called when new data arrives. When the
257   Sets the callback function that will be called when new data
266   Must be called when the application has received the data. The len
272 When a connection is idle (i.e., no data is either transmitted or
279 again when the connection has been idle for a while.
309   ATTENTION: When calling this from one of the TCP callbacks, make
316 connection are when there is a shortage of memory. The callback
370   Specifies a callback function that should be called when a UDP
380 We can give you some idea on how to proceed when using the raw API.
396   Give pointers to cleared ip_addr structures when using DHCP,
430   This is the administrative (= software) state of the netif, when the
441   When the system is running, you have to periodically call
470 E.g. when using the cs8900 driver, call cs8900if_service(ethif)
471 as frequently as possible. When using an RTOS let the cs8900 interrupt
486 when the packets have been enqueued for sending, data must be kept stable
493 but the stack/driver will/must copy PBUF_REF'ed data when enqueueing, while