| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/lwip/ |
| H A D | dhcp6.h | 61 /** track PCB allocation state */
67 /** if request config is triggered while another action is active, this keeps track of it */
72 /* @todo: add more members here to keep track of stateful DHCPv6 data, like lease times */
|
| H A D | dhcp.h | 71 /** track PCB allocation state */
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/test/fuzz/ |
| H A D | README | 9 the code and keeping track of which code is executed.
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/test/fuzz/ |
| H A D | README | 9 the code and keeping track of which code is executed.
|
| /nrf52832-nimble/packages/NimBLE-latest/apps/blecent/src/ |
| H A D | blecent.h | 84 /** Keeps track of where we are in the service discovery process. */
|
| H A D | blecent.c | 503 /* Initialize data structures to track connected peers. */ in blecent_entry()
|
| /nrf52832-nimble/packages/NimBLE-latest/docs/ |
| H A D | ble_sec.rst | 55 connection procedures that reduces the ability to track a LE device over
|
| H A D | index.rst | 45 difficult to track for outsiders
|
| /nrf52832-nimble/rt-thread/tools/kconfig-frontends/libs/parser/ |
| H A D | util.c | 34 /* write a dependency file as used by kbuild to track dependencies */
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/drivers/native/src/ |
| H A D | ble_hw.c | 32 /* We use this to keep track of which entries are set to valid addresses */
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/host/mesh/ |
| H A D | syscfg.yml | 129 in Progress, we need to keep track of how many hours has passed
322 Number of incomplete segment lists that we track for each LPN
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/include/lwip/ |
| H A D | dhcp.h | 73 /** track PCB allocation state */
|
| /nrf52832-nimble/rt-thread/components/net/uip/doc/ |
| H A D | uip-doc.txt | 283 application take part in retransmissions. uIP does not keep track of
361 should be made. As uIP does not keep track of packet contents after they have
946 into the right place in the buffer and a bit map is used to keep track
1050 As uIP does not keep track of packet contents after they have
|
| /nrf52832-nimble/rt-thread/components/drivers/usb/usbdevice/class/ |
| H A D | hid.c | 177 USAGE(1), 0xB5, // Next Track
178 USAGE(1), 0xB6, // Previous Track
|
| /nrf52832-nimble/packages/NimBLE-latest/docs/ble_hs/ |
| H A D | ble_hs_id.rst | 32 eavesdroppers to track its location.
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/host/mesh/src/ |
| H A D | net.h | 243 /* Timer to track duration in current IV Update state */
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/drivers/nrf52/src/ |
| H A D | ble_hw.c | 41 /* We use this to keep track of which entries are set to valid addresses */
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/drivers/nrf51/src/ |
| H A D | ble_hw.c | 35 /* We use this to keep track of which entries are set to valid addresses */
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/core/ipv6/ |
| H A D | ip6_frag.c | 84 * track of the various fragments.
473 /* Track the current number of pbufs current 'in-flight', in order to limit in ip6_reass()
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/core/ipv4/ |
| H A D | ip4_frag.c | 87 * track of the various fragments. (-> If the IP header doesn't need packing,
555 /* Track the current number of pbufs current 'in-flight', in order to limit in ip4_reass()
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/core/ipv4/ |
| H A D | ip4_frag.c | 91 * track of the various fragments. (-> If the IP header doesn't need packing,
604 /* Track the current number of pbufs current 'in-flight', in order to limit in ip4_reass()
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/core/ipv6/ |
| H A D | ip6_frag.c | 86 * track of the various fragments.
505 /* Track the current number of pbufs current 'in-flight', in order to limit in ip6_reass()
|
| /nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/src/core/ipv4/ |
| H A D | ip_frag.c | 85 * track of the various fragments. (-> If the IP header doesn't need packing,
550 /* Track the current number of pbufs current 'in-flight', in order to limit in ip_reass()
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/host/src/ |
| H A D | ble_l2cap_coc.c | 369 /* In data_offset we keep track on what we already sent. Need to remember in ble_l2cap_coc_continue_tx()
|
| /nrf52832-nimble/rt-thread/components/net/uip/doc/html/ |
| H A D | main.html | 68 … and lets the application take part in retransmissions. uIP does not keep track of packet contents…
80 …timer reaches zero, a retransmission should be made. As uIP does not keep track of packet contents…
377 …s copied into the right place in the buffer and a bit map is used to keep track of which fragments…
398 As uIP does not keep track of packet contents after they have been sent by the device driver, uIP r…
|