| /nrf52832-nimble/rt-thread/components/CMSIS/RTOS/ |
| H A D | cmsis_os.h | 24 its implementation.
39 …th <b>CAN BE CHANGED</b> can be adapted towards the needs of the actual CMSIS-RTOS implementation.
42 …b>MUST REMAIN UNCHANGED</b> cannot be altered. Otherwise the CMSIS-RTOS implementation is no longer
43 …te that some functions are optional and need not to be provided by every CMSIS-RTOS implementation.
186 /// \note CAN BE CHANGED: \b os_thread_cb is implementation specific in every CMSIS-RTOS.
190 /// \note CAN BE CHANGED: \b os_timer_cb is implementation specific in every CMSIS-RTOS.
194 /// \note CAN BE CHANGED: \b os_mutex_cb is implementation specific in every CMSIS-RTOS.
198 /// \note CAN BE CHANGED: \b os_semaphore_cb is implementation specific in every CMSIS-RTOS.
202 /// \note CAN BE CHANGED: \b os_pool_cb is implementation specific in every CMSIS-RTOS.
206 /// \note CAN BE CHANGED: \b os_messageQ_cb is implementation specific in every CMSIS-RTOS.
[all …]
|
| /nrf52832-nimble/rt-thread/components/net/uip/uip/ |
| H A D | lc-switch.h | 43 * Implementation of local continuations based on switch() statment
46 * This implementation of local continuations uses the C switch()
48 * function's body. The implementation is based on the fact that
52 * This implementation borrows heavily from Simon Tatham's coroutines
53 * implementation in C:
60 /* WARNING! lc implementation using switch() does not work if an
|
| H A D | lc-addrlabels.h | 43 * Implementation of local continuations based on the "Labels as
48 * This implementation of local continuations is based on a special
57 * implementation.
|
| /nrf52832-nimble/packages/NimBLE-latest/ext/tinycrypt/documentation/ |
| H A D | tinycrypt.rst | 8 The TinyCrypt Library provides an implementation for targeting constrained devices
89 the size of a platform-independent implementation, as presented in TinyCrypt.
157 * The current implementation does not support other key-lengths (such as 256
189 from them. As an extra precaution, the current implementation allows to at
203 To achieve minimal code size, TinyCrypt CCM implementation fixes q = 2,
213 produce the same authentication tag). TinyCrypt CCM implementation
216 * TinyCrypt CCM implementation accepts associated data of any length between
219 * TinyCrypt CCM implementation accepts:
238 * TinyCrypt ECC implementation is based on micro-ecc (see
294 the unpredictability of the implementation by using the NIST Statistical Test
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/netif/ |
| H A D | FILES | 9 A 6LoWPAN implementation as a netif.
12 A 6LoWPAN over Bluetooth Low Energy (BLE) implementation as netif,
16 A generic implementation of the SLIP (Serial Line IP)
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/lwip/ |
| H A D | ip6_zone.h | 27 * scopes, this rule exists for implementation simplicity. Violation of the
40 * implementation must also ensure that a packet with a scoped source and/or
43 * deliberately omitted in order to keep the implementation lightweight. The
150 * Should an implementation desire to implement a different policy, it can
166 * This default implementation follows the default model of RFC 4007, where
170 * scope, in this implementation it does not have an explicitly assigned zone
187 * This default implementation follows the default model of RFC 4007, where
190 * As such, this default implementation need not distinguish between different
210 * This default implementation follows the default model of RFC 4007, where
|
| H A D | sys.h | 127 * so both implementation types (recursive or non-recursive) should work.
275 * in your lwipopts.h, or ignore this parameter in your implementation
346 * example, a naive implementation could be:
358 * For now, we map straight to sys_arch implementation.
452 implementation */
465 * type sys_prot_t. If a particular port needs a different implementation, then
474 * mutex. The implementation should allow calling SYS_ARCH_PROTECT when
478 * different implementation, then this macro may be defined in sys_arch.h
488 * sys_arch.c. If a particular port needs a different implementation, then
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/apps/snmp/ |
| H A D | snmpv3_dummy.c | 45 * @param auth_algo is a pointer to u8_t. The implementation has to set this if user was found.
46 …* @param auth_key is a pointer to a pointer to a string. Implementation has to set this if user wa…
47 * @param priv_algo is a pointer to u8_t. The implementation has to set this if user was found.
48 …* @param priv_key is a pointer to a pointer to a string. Implementation has to set this if user wa…
|
| /nrf52832-nimble/rt-thread/components/net/uip/doc/html/ |
| H A D | a00124.html | 22 Implementation of local continuations based on switch() statment.
25 …implementation of local continuations uses the C switch() statement to resume execution of a funct…
26 This implementation borrows heavily from Simon Tatham's coroutines implementation in C: <a href="ht…
|
| H A D | files.html | 28 … <a href="a00174.html">[code]</a></td><td class="indexvalue">SMTP example implementation </td></tr>
34 …nt.c</a> <a href="a00180.html">[code]</a></td><td class="indexvalue">Implementation of the HTTP cl…
43 …ls.h</a> <a href="a00189.html">[code]</a></td><td class="indexvalue">Implementation of local conti…
44 …ch.h</a> <a href="a00190.html">[code]</a></td><td class="indexvalue">Implementation of local conti…
48 … <a href="a00194.html">[code]</a></td><td class="indexvalue">Protothreads implementation </td></tr>
49 …<a href="a00195.html">[code]</a></td><td class="indexvalue">Timer library implementation </td></tr>
58 …rp.c</a> <a href="a00204.html">[code]</a></td><td class="indexvalue">Implementation of the ARP Add…
|
| /nrf52832-nimble/rt-thread/components/net/uip/doc/ |
| H A D | uip-doc.txt | 46 The uIP implementation is designed to have only the absolute minimal
53 implementation running on a workstation-class machine. Under this
60 network citizens. The uIP TCP/IP implementation that is not tailored
100 application." A TCP/IP implementation that violates requirements of
156 for an architecture specific implementation of the two functions
164 implementation will have to do a number of 32-bit additions as part of
172 having an architecture specific implementation of the uip_add32()
227 simple Telnet server. It is possible to run the uIP implementation
480 The implementation of this application is shown below. The application
551 The implementation of this application is seen below. This
[all …]
|
| H A D | pt-doc.txt | 134 \section pt-impl Implementation
156 The standard C implementation requires only two bytes of state per
158 that is similar to Duff's device. This implementation does, however,
164 purpose. With this implementation, protothreads require 4 bytes of RAM
|
| /nrf52832-nimble/packages/NimBLE-latest/ext/tinycrypt/include/tinycrypt/ |
| H A D | cmac_mode.h | 1 /* cmac_mode.h -- interface to a CMAC implementation */
35 * @brief Interface to a CMAC implementation.
54 * an extra precaution, the current implementation allows to at most
61 * Usage: This implementation provides a "scatter-gather" interface, so that
69 * tc_cmac_struct with encryption key and buffer. Our implementation
|
| H A D | ecc_dh.h | 1 /* ecc_dh.h - TinyCrypt interface to EC-DH implementation */
61 * @brief -- Interface to EC-DH implementation.
63 * Overview: This software is an implementation of EC-DH. This implementation
|
| H A D | aes.h | 1 /* aes.h - TinyCrypt interface to an AES-128 implementation */
35 * @brief -- Interface to an AES-128 implementation.
73 * @note This implementation skips the additional steps required for keys
101 * @note This is the implementation of the straightforward inverse cipher
|
| H A D | ccm_mode.h | 1 /* ccm_mode.h - TinyCrypt interface to a CCM mode implementation */
35 * @brief Interface to a CCM mode implementation.
40 * TinyCrypt CCM implementation accepts:
50 * TinyCrypt CCM implementation accepts associated data of any length
56 * implementation accepts any even integer between 4 and 16, as
|
| H A D | ecc_dsa.h | 1 /* ecc_dh.h - TinyCrypt interface to EC-DSA implementation */
62 * @brief -- Interface to EC-DSA implementation.
64 * Overview: This software is an implementation of EC-DSA. This implementation
|
| /nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/ |
| H A D | UPGRADING | 50 * Separated timer implementation from sys.h/.c, moved to timers.h/.c;
51 Added timer implementation for NO_SYS==1, set NO_SYS_NO_TIMERS==1 if you
52 still want to use your own timer implementation for NO_SYS==0 (as before).
130 * Added timer implementation for NO_SYS==1 (may be disabled with NO_SYS_NO_TIMERS==1
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/include/lwip/ |
| H A D | sys.h | 127 * so both implementation types (recursive or non-recursive) should work.
283 * For now, we map straight to sys_arch implementation.
356 implementation */
369 * type sys_prot_t. If a particular port needs a different implementation, then
378 * mutex. The implementation should allow calling SYS_ARCH_PROTECT when
382 * different implementation, then this macro may be defined in sys_arch.h
392 * sys_arch.c. If a particular port needs a different implementation, then
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/ |
| H A D | UPGRADING | 36 * The IPv6 implementation now supports address scopes. (See LWIP_IPV6_SCOPES documentation
81 * Added an implementation for posix sendmsg()
184 * Separated timer implementation from sys.h/.c, moved to timers.h/.c;
185 Added timer implementation for NO_SYS==1, set NO_SYS_NO_TIMERS==1 if you
186 still want to use your own timer implementation for NO_SYS==0 (as before).
264 * Added timer implementation for NO_SYS==1 (may be disabled with NO_SYS_NO_TIMERS==1
|
| /nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/src/include/lwip/ |
| H A D | sys.h | 202 /** For now, we map straight to sys_arch implementation. */
244 implementation */
255 * type sys_prot_t. If a particular port needs a different implementation, then
262 * mutex. The implementation should allow calling SYS_ARCH_PROTECT when
266 * different implementation, then this macro may be defined in sys_arch.h
274 * sys_arch.c. If a particular port needs a different implementation, then
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/ |
| H A D | UPGRADING | 38 * Added an implementation for posix sendmsg()
141 * Separated timer implementation from sys.h/.c, moved to timers.h/.c;
142 Added timer implementation for NO_SYS==1, set NO_SYS_NO_TIMERS==1 if you
143 still want to use your own timer implementation for NO_SYS==0 (as before).
221 * Added timer implementation for NO_SYS==1 (may be disabled with NO_SYS_NO_TIMERS==1
|
| H A D | README | 3 lwIP is a small independent implementation of the TCP/IP protocol
8 The focus of the lwIP TCP/IP implementation is to reduce the RAM usage
40 * iPerf server implementation
|
| /nrf52832-nimble/packages/NimBLE-latest/ |
| H A D | .rat-excludes | 24 # Queue implementation - BSD License
27 # mbuf implementation - BSD License
|
| /nrf52832-nimble/rt-thread/components/net/freemodbus/ |
| H A D | Changelog.txt | 50 in discrete input registers implementation where the frame was not parsed
82 can lead to a memory leak depending upon the implementation of the
96 function (0x17). The implementation simply makes two callbacks
249 a Modbus/TCP implementation.
252 - OTHER: The implementation of eMBClose to shutdown the protocol stack
293 implementation because no one actually uses it and the CPU
|