Lines Matching full:to
6 to use for communication with the TCP/IP code:
12 to be used without an operating system that implements zero-copy send and
18 to use the lwIP stack. It is quite similar to the BSD socket API. The
25 currently it is built on top of the sequential API. It is meant to
26 provide all functions needed to run socket API applications running
27 on other platforms (e.g. unix / windows etc.). However, due to limitations
64 If SYS_LIGHTWEIGHT_PROT is set to 1 and
65 LWIP_ALLOW_MEM_FREE_FROM_OTHER_CONTEXT is set to 1,
74 The raw TCP/IP interface allows the application program to integrate
85 the raw TCP/IP interface are more difficult to understand. Still, this
95 TCP and UDP), the later refers to processing raw Ethernet or IP data
105 invoked by the lwIP core when activity related to that application
106 occurs. A particular application may register to be notified via a
109 closed, etc. An application can provide a callback function to perform
113 argument. Also, in order to be able to keep program specific state,
121 Specifies the program specific state that should be passed to all
124 that will be passed to the callbacks.
129 The functions used for setting up connections is similar to that of
132 tcp_new() function. This PCB can then be either set to listen for new
133 incoming connections or be explicitly connected to another host.
143 Binds the pcb to a local IP address and port number. The IP address
144 can be specified as IP_ADDR_ANY in order to bind the connection to
147 If another connection is bound to the same port, the function will
152 Commands a pcb to start listening for incoming connections. When an
154 tcp_accept() function will be called. The pcb will have to be bound
155 to a local port with the tcp_bind() function.
158 the one passed as an argument to the function will be
166 passed as an argument to tcp_listen() will not be deallocated.
171 in the listen queue to the value specified by the backlog argument.
172 To use it, your need to set TCP_LISTEN_BACKLOG=1 in your lwipopts.h.
186 Sets up the pcb to connect to the remote host and sends the
190 the connection to be properly setup. Instead, it will call the
205 TCP data is sent by enqueueing the data with a call to
206 tcp_write(). When the data is successfully transmitted to the remote
207 host, the application will be notified with a call to a specified
213 Enqueues the data pointed to by the argument dataptr. The length of
216 for the data to be copied into. If this flag is not given, no new memory
221 the PSH flag is set in the last segment created by this call to tcp_write.
230 The proper way to use this function is to call the function with at
241 host. The len argument passed to the callback function gives the
249 application has taken the data, it has to call the tcp_recved()
250 function to indicate that TCP can advertise increase the receive
258 arrives. The callback function will be passed a NULL pbuf to
260 there are no errors and the callback function is to return
276 as a method of waiting for memory to become available. For instance,
277 if a call to tcp_write() has failed because memory wasn't available,
278 the application may use the polling functionality to call tcp_write()
286 be called to poll the application. The interval is specified in
302 The pcb is deallocated by the TCP code after a call to tcp_close().
306 Aborts the connection by sending a RST (reset) segment to the remote
317 function to be called is set using the tcp_err() function.
322 The error callback function does not get the pcb passed to it as a
328 The UDP interface is similar to that of TCP, but due to the lower
334 pcb is not active until it has either been bound to a local address
335 or connected to a remote address.
344 Binds the pcb to a local address. The IP-address argument "ipaddr"
345 can be IP_ADDR_ANY to indicate that it should listen to any local IP
380 We can give you some idea on how to proceed when using the raw API.
394 Adds your network interface to the netif_list. Allocate a struct
395 netif and pass a pointer to this structure as the first argument.
396 Give pointers to cleared ip_addr structures when using DHCP,
399 The init function pointer must point to a initialization function for
413 For Ethernet drivers, the input function pointer must point to the lwIP
441 When the system is running, you have to periodically call
443 the stack; add this to your main loop or equivalent.
448 The first thing you want to optimize is the lwip_standard_checksum()
452 There are C examples given in inet.c or you might want to
454 introduction to this subject.
461 If you #define them to htons() and htonl(), you should
462 #define LWIP_DONT_PROVIDE_BYTEORDER_FUNCTIONS to prevent lwIP from
468 buffer overflows are likely to occur.
474 to match your application and network.
476 For a production release it is recommended to set LWIP_STATS to 0.
478 high values to the memory options.
484 To achieve zero-copy on transmit, the data passed to the raw API must
489 This implies that PBUF_RAM/PBUF_POOL pbufs passed to raw-API send functions
494 PBUF_ROM-pbufs are just enqueued (as ROM-data is expected to never change).
496 Also, data passed to tcp_write without the copy-flag must not be changed!