| /nrf52832-nimble/rt-thread/components/net/freemodbus/port/ |
| H A D | portevent_m.c | 127 * @note This code is use OS's event mechanism for modbus master protocol stack. in vMBMasterErrorCBRespondTimeout()
149 * @note This code is use OS's event mechanism for modbus master protocol stack. in vMBMasterErrorCBReceiveData()
171 * @note This code is use OS's event mechanism for modbus master protocol stack. in vMBMasterErrorCBExecuteFunction()
188 * @note This code is use OS's event mechanism for modbus master protocol stack. in vMBMasterCBRequestScuuess()
201 * @note If you are use OS, you can use OS's event mechanism. Otherwise you have to run
|
| /nrf52832-nimble/rt-thread/documentation/doxygen/ |
| H A D | kernel.h | 81 * by priority or FIFO. There are two flags to indicate this mechanism.
90 * - The event mechanism is used to awake a thead by setting one or more corresponding
136 * In order to trace and record RT-Thread activity in runtime, a hook mechanism
|
| /nrf52832-nimble/rt-thread/components/net/uip/doc/ |
| H A D | uip-doc.txt | 99 MUST be a mechanism for reporting soft TCP error conditions to the
109 and the stack, such as the soft error reporting mechanism and
976 querying host parameters. Its main use is, however, the echo mechanism
1011 Most TCP implementations use a sliding window mechanism for sending
1025 specifications. Removing the sliding window mechanism does not affect
1079 probing mechanism.
1094 TCP's urgent data mechanism provides an application-to-application
1095 notification mechanism, which can be used by an application to mark
1102 because it requires an asynchronous notification mechanism in an
|
| H A D | pt-doc.txt | 114 mechanism to protothreads are Python generators. These are also
|
| /nrf52832-nimble/rt-thread/components/dfs/filesystems/jffs2/cyg/compress/tests/ |
| H A D | zlib1.c | 88 "1.4. \"Electronic Distribution Mechanism\" means a\n"
89 "mechanism generally accepted in the software development\n"
|
| H A D | zlib2.c | 174 "1.4. \"Electronic Distribution Mechanism\" means a\n"
175 "mechanism generally accepted in the software development\n"
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/include/lwip/apps/ |
| H A D | httpd.h | 77 * Requests intended for use by this CGI mechanism must be sent using the GET
134 * Note that the behavior of this SSI mechanism is somewhat different from the
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/lwip/apps/ |
| H A D | httpd.h | 78 * Requests intended for use by this CGI mechanism must be sent using the GET
143 * Note that the behavior of this SSI mechanism is somewhat different from the
|
| /nrf52832-nimble/rt-thread/components/dfs/filesystems/jffs2/cyg/compress/src/ |
| H A D | uncompr.c | 21 by some mechanism outside the scope of this compression library.)
|
| H A D | algorithm.txt | 38 mechanism. After a match of length N has been found, deflate() searches for
|
| H A D | deflate.h | 173 * smaller than this value. This mechanism is used only for compression
|
| /nrf52832-nimble/packages/NimBLE-latest/docs/ |
| H A D | ble_sec.rst | 37 mechanism is used to both discover the devices as well as to exchange
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/host/ |
| H A D | syscfg.yml | 378 underlying storage mechanism.
385 mechanism.
|
| /nrf52832-nimble/rt-thread/components/net/uip/doc/html/ |
| H A D | main.html | 37 …n in any segment" and an example of the second kind is "There MUST be a mechanism for reporting so…
38 …between the application and the stack, such as the soft error reporting mechanism and dynamically …
382 …ns and for querying host parameters. Its main use is, however, the echo mechanism which is used by…
390 Most TCP implementations use a sliding window mechanism for sending data. Multiple data segments ar…
392 … is not required by the TCP specifications. Removing the sliding window mechanism does not affect …
401 …not accept any data at all, the stack initiates the zero window probing mechanism.<h4><a class="an…
406 TCP's urgent data mechanism provides an application-to-application notification mechanism, which ca…
407 … of the implementation because it requires an asynchronous notification mechanism in an otherwise …
|
| /nrf52832-nimble/nordic/nrfx/drivers/include/ |
| H A D | nrfx_pwm.h | 155 When this mechanism is used together with
227 * To take advantage of the looping mechanism in the PWM peripheral, both
|
| H A D | nrfx_qspi.h | 123 * mechanism.
|
| /nrf52832-nimble/rt-thread/components/libc/compilers/armlibc/ |
| H A D | stubs.c | 120 * signalling no error (i.e. the top-bit-set mechanism need never
|
| /nrf52832-nimble/nordic/nrfx/hal/ |
| H A D | nrf_nfct.h | 620 * @details The automatic collision resolution mechanism as defined in ISO 14443-3 and NFC Forum
631 * @details The automatic collision resolution mechanism as defined in ISO 14443-3 and NFC Forum
639 * @details The automatic collision resolution mechanism as defined in ISO 14443-3 and NFC Forum
|
| H A D | nrf_kmu.h | 59 …ROR) ///< No key slot selected or no destination address defined or error during push mechanism.
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/host/include/host/ |
| H A D | ble_gap.h | 794 * event-reporting mechanism.
1001 * callback as its event-reporting mechanism.
1057 * callback as its event-reporting mechanism.
|
| /nrf52832-nimble/rt-thread/components/net/freemodbus/ |
| H A D | lgpl.txt | 298 b) Use a suitable shared library mechanism for linking with the
299 Library. A suitable mechanism is one that (1) uses at run time a
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/include/lwip/ |
| H A D | pbuf.h | 58 /* @todo: We need a mechanism to prevent wasting memory in every pbuf
|
| /nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/src/include/lwip/ |
| H A D | sys.h | 243 mechanism than using semaphores. Otherwise semaphores can be used for
|
| /nrf52832-nimble/rt-thread/ |
| H A D | ChangeLog.md | 141 …* HOST, optimize the USB HOST timeout mechanism; fix the un-alignment visit issue in F4xx-HAL USB …
142 …ess issue in some platforms; optimize CDC VCOM classes, add the timeout mechanism and ID definitio…
263 * Change the registration mechanism of USB Class Driver and Class Driver can be registered in packa…
|
| /nrf52832-nimble/rt-thread/libcpu/arm/armv6/ |
| H A D | mmu.c | 263 the hardware page translation mechanism, Subpage AP bits disabled */ in mmu_enable()
|