Searched refs:received (Results 1 - 13 of 13) sorted by relevance
/seL4-camkes-master/projects/camkes/apps/socket/components/Receiver/src/ |
H A D | receiver.c | 19 int received = 0; local 20 while (!received) { 24 received = 1;
|
/seL4-camkes-master/projects/camkes/apps/socket/components/Transport/src/ |
H A D | transport.c | 25 int received = 0; local 26 while (!received) { 33 received = 1;
|
/seL4-camkes-master/projects/projects_libs/libringbuffer/src/ |
H A D | ringbuffer.c | 91 size_t received = 0; local 97 return received; 112 size_t received = 0; local 119 return received;
|
/seL4-camkes-master/projects/lwip/test/unit/tcp/ |
H A D | tcp_helper.c | 195 u32_t i, received; local 201 received = counters->recved_bytes; 205 EXPECT_RET(data[i] == counters->expected_data[received]); 206 received++; 209 EXPECT(received == counters->recved_bytes + p->tot_len);
|
/seL4-camkes-master/kernel/manual/parts/ |
H A D | ipc.tex | 22 The message words are sent to or received from a thread by placing them in its \emph{message registers}. 41 manner in which capabilities were received. It is described in 59 endpoint capabilities received} 119 message received from another thread via the endpoint. 276 it has been performing a \apifunc{seL4\_Recv}{sel4_recv} and just received the 285 In particular, it is guaranteed that the reply received by the caller comes from 286 the thread that received the call without having to check any kind of badge.
|
H A D | notifications.tex | 61 endpoint. To distinguish whether the received message was a notification
|
H A D | objects.tex | 206 message is delivered and a reply message is received.
|
H A D | threads.tex | 252 have received a scheduling context through donation) using
|
/seL4-camkes-master/projects/picotcp/docs/user_manual/ |
H A D | chap_api_tftp.tex | 14 Function pico$\_$tftp$\_$listen must be used to start the server with a proper callback that should be provided by the user. To reject a request received by the server the server callback must call pico$\_$tftp$\_$reject$\_$request. 36 Single chunk of data are received using pico$\_$tftp$\_$get and transmitted with the use of the function pico$\_$tftp$\_$put. 46 transfer request received from the network, and the call will pass the information about: 264 In order to ask Transfer size Option value PICO$\_$TFTP$\_$OPTION$\_$FILE must be used; it may be used for example for example in receiver callback for calculation of remaining bytes to be received to complete the current transfer. 310 Note that timeout and filesize are modified only if the corresponding option is found in the received message. 391 \item \texttt{PICO$\_$TFTP$\_$EV$\_$OPT} Option acknowledge has been received. 502 \item \texttt{PICO$\_$TFTP$\_$EV$\_$OPT} Option acknowledge has been received. 568 printf("Information about file size has not been received"\n); 710 \item \texttt{filename} - The name of the file to be received. 801 This function returns the number of received byte [all...] |
H A D | chap_api_ipv4.tex | 477 This function sends out a number of ping echo requests and checks if the replies are received correctly. 479 If a timeout expires before a reply is received, the callback is called with the error condition. 492 \item \texttt{timeout} - Timeout period untill reply received (in ms)
|
H A D | chap_api_sock.tex | 34 \item \texttt{PICO$\_$SOCK$\_$EV$\_$CONN} - triggered when connection is established (TCP only). This event is received either after a successful call to \texttt{pico$\_$socket$\_$connect} to indicate that the connection has been established, or on a listening socket, indicating that a call to \texttt{pico$\_$socket$\_$accept} may now be issued in order to accept the incoming connection from a remote host. 35 \item \texttt{PICO$\_$SOCK$\_$EV$\_$CLOSE} - triggered when a FIN segment is received (TCP only). This event indicates that the other endpont has closed the connection, so the local TCP layer is only allowed to send new data until a local shutdown or close is initiated. PicoTCP is able to keep the connection half-open (only for sending) after the FIN packet has been received, allowing new data to be sent in the TCP CLOSE$\_$WAIT state. 70 \item \texttt{buf} - Void pointer to the start of the buffer where the received data will be stored 298 \item \texttt{info} - Extended information about the incoming packet containing this datagram. The device where the packet was received is pointed by info->dev, the maximum TTL for the packet is stored in info->ttl, and finally the field info->tos keeps track of the flags in IP header's QoS. 321 printf("Socket received a datagram via device %s, ttl:%d, tos: %08x\n",
|
H A D | chap_api_mdns.tex | 153 \item \texttt{callback} - Callback to call when records are found or answers to the query are received. This functions can get called multiple times when multiple answers are possible (e.g. with shared records). It's up to the application to aggregate all these received answers, this is possible with a static variable of the type pico$\_$mdns$\_$rtree.
|
H A D | chap_api_dhcp_c.tex | 156 \item \texttt{index} - the indes of the domain name server received. Can be either "0" or "1".
|
Completed in 154 milliseconds