Lines Matching full:be
12 to be used without an operating system that implements zero-copy send and
28 in the specification of this API, there might be incompatibilities
37 environment, raw API functions MUST only be called from the core thread
43 As such, the list of functions that may be called from
54 Additionaly, memory (de-)allocation functions may be
62 not be shared among multiple threads without proper locking.
66 pbuf_free() may also be called from another thread or
68 be called from an ISR: otherwise, the HEAP is only
86 is the preferred way of writing applications that should be small in
89 All APIs can be used simultaneously by different application
106 occurs. A particular application may register to be notified via a
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.
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.
144 can be specified as IP_ADDR_ANY in order to bind the connection to
154 tcp_accept() function will be called. The pcb will have to be bound
158 the one passed as an argument to the function will be
166 passed as an argument to tcp_listen() will not be deallocated.
178 Specified the callback function that should be called when a new
190 the connection to be properly setup. Instead, it will call the
192 when the connection is established. If the connection could not be
196 will be called.
207 host, the application will be notified with a call to a specified
214 the data is passed as the len parameter. The apiflags can be one or more of:
215 - TCP_WRITE_FLAG_COPY: indicates whether the new memory should be allocated
216 for the data to be copied into. If this flag is not given, no new memory
217 should be allocated and the data should only be referenced by pointer. This
228 be retrieved with the tcp_sndbuf() function.
239 Specifies the callback function that should be called when data has
257 Sets the callback function that will be called when new data
258 arrives. The callback function will be passed a NULL pbuf to
266 Must be called when the application has received the data. The len
274 specified callback function. This can be used either as a watchdog
286 be called to poll the application. The interval is specified in
289 be polled every 5 seconds.
317 function to be called is set using the tcp_err() function.
333 Creates a new UDP pcb which can be used for UDP communication. The
345 can be IP_ADDR_ANY to indicate that it should listen to any local IP
370 Specifies a callback function that should be called when a UDP
377 cannot be given because it depends on additional initializations for
397 or fill them with sane numbers otherwise. The state pointer may be NULL.
424 Ethernet interface. This function must be called even if you don't know
431 netif is fully configured this function must be called.
456 Other significant improvements can be made by supplying
486 when the packets have been enqueued for sending, data must be kept stable
490 must *not* be reused by the application unless their ref-count is 1.
492 For no-copy pbufs (PBUF_ROM/PBUF_REF), data must be kept unchanged, too,
496 Also, data passed to tcp_write without the copy-flag must not be changed!
498 Therefore, be careful which type of PBUF you use and if you copy TCP data