| /nrf52832-nimble/nordic/nrfx/drivers/include/ |
| H A D | nrfx_twi.h | 110 NRFX_TWI_EVT_ADDRESS_NACK, ///< Error event: NACK received after sending the address.
111 NRFX_TWI_EVT_DATA_NACK ///< Error event: NACK received after sending a data byte.
236 * @brief Function for sending data to a TWI slave.
252 * @retval NRFX_ERROR_DRV_TWI_ERR_ANACK If NACK received after sending the address in polling mode.
253 * @retval NRFX_ERROR_DRV_TWI_ERR_DNACK If NACK received after sending a data byte in polling mode.
276 …* @retval NRFX_ERROR_DRV_TWI_ERR_ANACK If NACK received after sending the address in polling mo…
277 …* @retval NRFX_ERROR_DRV_TWI_ERR_DNACK If NACK received after sending a data byte in polling mo…
312 * @retval NRFX_ERROR_DRV_TWI_ERR_ANACK If NACK received after sending the address.
313 * @retval NRFX_ERROR_DRV_TWI_ERR_DNACK If NACK received after sending a data byte.
|
| H A D | nrfx_twim.h | 120 NRFX_TWIM_EVT_ADDRESS_NACK, ///< Error event: NACK received after sending the address.
121 NRFX_TWIM_EVT_DATA_NACK ///< Error event: NACK received after sending a data byte.
246 * @brief Function for sending data to a TWI slave.
270 * @retval NRFX_ERROR_DRV_TWI_ERR_ANACK If NACK received after sending the address in polling mode.
271 * @retval NRFX_ERROR_DRV_TWI_ERR_DNACK If NACK received after sending a data byte in polling mode.
296 …* @retval NRFX_ERROR_DRV_TWI_ERR_ANACK If NACK received after sending the address in polling mo…
297 …* @retval NRFX_ERROR_DRV_TWI_ERR_DNACK If NACK received after sending a data byte in polling mo…
351 * @retval NRFX_ERROR_DRV_TWI_ERR_ANACK If NACK received after sending the address.
352 * @retval NRFX_ERROR_DRV_TWI_ERR_DNACK If NACK received after sending a data byte.
|
| H A D | nrfx_qspi.h | 182 * and sending of operation data are finished.
209 * and sending of operation data are finished.
245 …* @brief Function for sending operation code, sending data, and receiving data from the memory dev…
263 …* @brief Function for sending operation code and data to the memory device with simpler configurat…
268 * @param[in] opcode Operation code. Sending first.
|
| /nrf52832-nimble/rt-thread/components/net/uip/uip/ |
| H A D | uip-split.h | 48 * maximum achievable throughput for sending data from uIP.
53 * receivers. This improves the throughput when sending data from uIP
57 * forwarding) for sending packets. Therefore, the uip-fw module must
|
| /nrf52832-nimble/rt-thread/components/net/uip/doc/ |
| H A D | uip-doc.txt | 224 simultaneous connections. A device that will be sending large e-mails
293 both for sending data and retransmitting data. Also, it is important
335 \subsubsection senddata Sending Data
337 When sending data, uIP adjusts the length of the data sent by the
373 a way that the same code is used both for sending data and
542 remote host, it responds by sending an "ok" back.
804 data by sending out the message "Hello world!". To illustrate how to
872 "STATE_HELLO", in which the application is sending the "Hello" part of
873 the message, or "STATE_WORLD", in which the application is sending the
904 Finally, the senddata() function takes care of actually sending the
[all …]
|
| /nrf52832-nimble/rt-thread/components/net/uip/doc/html/ |
| H A D | a00154.html | 22 …ight TCP segments seriously reduces the maximum achievable throughput for sending data from uIP.<p>
23 …rithm is not invoked at TCP receivers. This improves the throughput when sending data from uIP by …
24 The uip-split module uses the uip-fw module (uIP IP packet forwarding) for sending packets. Therefo…
|
| H A D | main.html | 58 …nd the maximum amount of simultaneous connections. A device that will be sending large e-mails whi…
68 …ication can be written in such a way that the same code is used both for sending data and retransm…
75 Sending Data</a></h4>
76 When sending data, uIP adjusts the length of the data sent by the application according to the avai…
81 …ication can be written in such a way that the same code is used both for sending data and retransm…
132 …the application receives any new data from the remote host, it responds by sending an "ok" back.<p>
305 …ts for any data to arrive on the connection, and responds to the data by sending out the message "…
364 … in which the application is sending the "Hello" part of the message, or "STATE_WORLD", in which t…
369 Finally, the senddata() function takes care of actually sending the data that is to be sent. It is …
380 … or multicast packets. uIP current supports broadcast packets as well as sending multicast packets…
[all …]
|
| H A D | a00200.html | 68 <a name="l00048"></a>00048 <span class="comment"> * maximum achievable throughput for sending data …
73 …53 <span class="comment"> * receivers. This improves the throughput when sending data from uIP</sp…
77 <a name="l00057"></a>00057 <span class="comment"> * forwarding) for sending packets. Therefore, the…
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/host/mesh/include/mesh/ |
| H A D | access.h | 122 /** Message sending context. */
133 /** Destination address of a received message. Not used for sending. */
136 /** Received TTL value. Not used for sending. */
139 /** Force sending reliably by using segment acknowledgement */
|
| /nrf52832-nimble/rt-thread/components/net/freemodbus/modbus/ascii/ |
| H A D | mbascii.c | 70 STATE_TX_DATA, /*!< Sending of data (Address, Data, LRC). */
193 * frame on the network. We have to abort sending the frame. in eMBASCIISend()
338 /* Start of transmission. The start of a frame is defined by sending in xMBASCIITransmitFSM()
378 /* Finish the frame by sending a LF character. */ in xMBASCIITransmitFSM()
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/host/mesh/src/ |
| H A D | mesh.c | 144 /* Enable unprovisioned beacon sending */ in bt_mesh_prov_enable()
228 /* Enable unprovisioned beacon sending */ in bt_mesh_init()
|
| H A D | transport.c | 274 BT_ERR("Sending segment failed"); in seg_tx_send_unacked()
397 BT_DBG("Sending %u/%u", seg_o, tx->seg_n); in send_seg()
403 BT_ERR("Sending segment failed"); in send_seg()
981 BT_WARN("Not sending ack when LPN is enabled"); in send_ack()
989 BT_WARN("Not sending ack for non-unicast address"); in send_ack()
1089 * has apparently started sending a new SDU. in seg_rx_find()
1231 /* We ignore instead of sending block ack 0 since the in trans_seg()
1399 * queued for sending, however that's fine since then the in bt_mesh_trans_recv()
1401 * we still need to go through the actual sending to the bearer and in bt_mesh_trans_recv()
|
| H A D | adv.h | 49 /* For transport layer segment sending */
|
| H A D | friend.c | 169 /* Cancel the sending if necessary */ in friend_clear()
594 BT_DBG("Re-sending last PDU"); in bt_mesh_friend_poll()
982 /* Friend Offer doesn't follow the re-sending semantics */ in buf_send_start()
996 BT_WARN("Another request before previous completed sending"); in buf_send_end()
1024 BT_DBG("Sending frnd->last %p", frnd->last); in friend_timeout()
1042 BT_DBG("Sending buf %p from Friend Queue of LPN 0x%04x", in friend_timeout()
|
| /nrf52832-nimble/rt-thread/components/drivers/i2c/ |
| H A D | i2c-bit-ops.c | 327 bit_dbg("NACK: sending first addr\n"); in i2c_bit_send_address()
335 bit_dbg("NACK: sending second addr\n"); in i2c_bit_send_address()
347 bit_dbg("NACK: sending repeated addr\n"); in i2c_bit_send_address()
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/lwip/ |
| H A D | ip6_frag.h | 67 * completing reassembly or sending an ICMPv6 reply. The last part is true even
101 /* In this case we still need the buffer, for sending ICMPv6 replies. */
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/apps/http/ |
| H A D | httpd.c | 212 TAG_SENDING /* Sending tag replacement string */
668 /* ensure nagle doesn't interfere with sending all data as fast as possible: */ in http_eof()
992 * - HTTP_DATA_TO_SEND_CONTINUE: continue with sending HTTP body
1049 /* Have we finished sending this string? */
1065 * (which would happen when sending files from async read). */
1395 /* Next time through, we are going to be sending data
1397 * sending here or the insert string. */
1412 /* we would include the tag in sending */
1440 * We have found a valid tag and are in the process of sending
1453 /* we would include the tag in sending */
[all …]
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/apps/httpd/ |
| H A D | httpd.c | 208 TAG_SENDING /* Sending tag replacement string */
654 /* ensure nagle doesn't interfere with sending all data as fast as possible: */ in http_eof()
971 * - HTTP_DATA_TO_SEND_CONTINUE: continue with sending HTTP body
1022 /* Have we finished sending this string? */
1038 * (which would happen when sending files from async read). */
1358 /* Next time through, we are going to be sending data
1360 * sending here or the insert string. */
1375 /* we would include the tag in sending */
1405 * We have found a valid tag and are in the process of sending
1418 /* we would include the tag in sending */
[all …]
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/apps/sntp/ |
| H A D | sntp.c | 315 LWIP_DEBUGF(SNTP_DEBUG_STATE, ("sntp_try_next_server: Sending request to server %"U16_F"\n", in sntp_try_next_server()
442 LWIP_DEBUGF(SNTP_DEBUG_STATE, ("sntp_send_request: Sending request to server\n")); in sntp_send_request()
447 /* free the pbuf after sending it */ in sntp_send_request()
475 LWIP_DEBUGF(SNTP_DEBUG_STATE, ("sntp_dns_found: Server address resolved, sending request\n")); in sntp_dns_found()
|
| /nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/src/netif/ppp/ |
| H A D | chap.c | 225 * ChapChallengeTimeout - Timeout expired on sending challenge.
232 /* if we aren't sending challenges, don't worry. then again we */ in ChapChallengeTimeout()
252 * ChapResponseTimeout - Timeout expired on sending response.
259 /* if we aren't sending a response, don't worry. */ in ChapResponseTimeout()
276 /* if we aren't sending a response, don't worry. */ in ChapRechallenge()
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/ |
| H A D | FEATURES | 10 …s: congestion control, RTT estimation and fast recovery/fast retransmit, sending SACKs (since v2.1…
|
| /nrf52832-nimble/rt-thread/components/utilities/zmodem/ |
| H A D | sz.c | 3 * the implemention of sending files to the remote computers
156 /* start sending files */ in zsend_files()
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/netif/ppp/ |
| H A D | mppe.c | 173 * We received a CCP Reset-Request (actually, we are sending a Reset-Ack),
347 * Signal the peer to rekey (by sending a CCP Reset-Request). in mppe_decompress()
403 * Take LCP down if the peer is sending too many bogons. in mppe_decompress()
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/netif/ppp/ |
| H A D | mppe.c | 173 * We received a CCP Reset-Request (actually, we are sending a Reset-Ack),
347 * Signal the peer to rekey (by sending a CCP Reset-Request). in mppe_decompress()
403 * Take LCP down if the peer is sending too many bogons. in mppe_decompress()
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/core/ |
| H A D | tcp_out.c | 126 /* If we're sending a packet, update the announced right window edge */ in tcp_output_alloc_header()
352 * Write data for sending (but does not send it immediately).
360 * @param arg Pointer to the data to be enqueued for sending.
936 /* let tcp_fasttmr retry sending this ACK */ in tcp_send_empty_ack()
945 ("tcp_output: sending ACK for %"U32_F"\n", pcb->rcv_nxt)); in tcp_send_empty_ack()
974 /* let tcp_fasttmr retry sending this ACK */ in tcp_send_empty_ack()
1095 /* Stop sending if the nagle algorithm would prevent it in tcp_output()
1538 LWIP_DEBUGF(TCP_DEBUG, ("tcp_keepalive: sending KEEPALIVE probe to ")); in tcp_keepalive()
1597 LWIP_DEBUGF(TCP_DEBUG, ("tcp_zero_window_probe: sending ZERO WINDOW probe to ")); in tcp_zero_window_probe()
|