/nrf52832-nimble/rt-thread/tools/kconfig-frontends/ |
H A D | README | 5 source tree, with very minor changes to adapt them to being built out of 14 most welcome, of course! Most notably, because this is my very first
|
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/lwip/priv/ |
H A D | mem_priv.h | 55 * This is VERY SLOW but also very helpful.
|
/nrf52832-nimble/rt-thread/components/net/uip/doc/ |
H A D | uip-doc.txt | 55 are very rarely used in such situations. Many of those mechanisms are 111 connections. Since there are only very few applications that make use 204 running in parallel. This is because uIP advertises a very small 470 This section presents a number of very simple uIP applications. The 473 \subsection example1 A Very Simple Application 475 This first example shows a very simple application. The application 684 This example shows a very simple file server application that listens 801 The following very simple application serves as an example of how the 939 because they are very uncommon, any IP options in received packets are 979 The ICMP implementation in uIP is very simple as itis restricted to [all …]
|
H A D | pt-doc.txt | 45 - Very small RAM overhead - only two bytes per protothread 95 protothreads are very lightweight: a protothread does not require its
|
/nrf52832-nimble/rt-thread/src/ |
H A D | timer.c | 372 /* Interestingly, this super simple timer insert counter works very very in rt_timer_start() 373 * well on distributing the list height uniformly. By means of "very very in rt_timer_start() 374 * well", I mean it beats the randomness of timer->timeout_tick very easily in rt_timer_start()
|
/nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/src/core/ipv6/ |
H A D | README | 1 IPv6 support in lwIP is very experimental.
|
/nrf52832-nimble/rt-thread/examples/nanopb/ |
H A D | simple.proto | 1 // A very simple protocol definition, consisting of only
|
/nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/include/lwip/priv/ |
H A D | memp_priv.h | 55 * This is VERY SLOW but also very helpful. */
|
/nrf52832-nimble/rt-thread/components/dfs/filesystems/jffs2/kernel/linux/ |
H A D | TODO | 2 This contains a very limited set of Linux-compatibility headers, initially
|
/nrf52832-nimble/rt-thread/components/net/uip/ |
H A D | README | 1 uIP is a very small implementation of the TCP/IP stack that is written
|
H A D | uip-1.0-changelog.txt | 4 * Very rudimentary IPv6 support
|
/nrf52832-nimble/rt-thread/components/net/uip/doc/html/ |
H A D | main.html | 32 …s assumption, it is possible to remove certain TCP/IP mechanisms that are very rarely used in such… 38 …nfigurable type-of-service bits for TCP connections. Since there are only very few applications th… 56 …ple connections are running in parallel. This is because uIP advertises a very small receiver wind… 112 This section presents a number of very simple uIP applications. The uIP code distribution contains … 113 A Very Simple Application</a></h3> 114 This first example shows a very simple application. The application listens for incoming connection… 229 This example shows a very simple file server application that listens to two ports and uses the por… 305 The following very simple application serves as an example of how the application handler functions… 375 …e there are no IP options that are strictly required and because they are very uncommon, any IP op… 383 The ICMP implementation in uIP is very simple as itis restricted to only implement ICMP echo messag… [all …]
|
H A D | a00164.html | 20 The uIP web server is a very simplistic implementation of an HTTP server. 22 It can serve web pages and files from a read-only ROM filesystem, and provides a very small scripti…
|
H A D | a00143.html | 46 <tr><td class="mdescLeft"> </td><td class="mdescRight">The uIP web server is a very simplistic…
|
/nrf52832-nimble/rt-thread/components/drivers/include/ipc/ |
H A D | ringblk_buf.h | 18 * is very suitable for put block and get block by a certain order. Such as DMA block transmit,
|
/nrf52832-nimble/packages/NimBLE-latest/docs/mesh/ |
H A D | index.rst | 20 making it very power efficient (battery powered low-power nodes that don't relay messages can opera…
|
/nrf52832-nimble/rt-thread/components/dfs/filesystems/jffs2/src/ |
H A D | compr_rtime.c | 13 * Very simple lz77-ish encoder.
|
/nrf52832-nimble/packages/NimBLE-latest/ext/tinycrypt/src/ |
H A D | cbc_mode.c | 100 * contiguous. This allows for a very efficient decryption algorithm in tc_cbc_mode_decrypt()
|
/nrf52832-nimble/packages/NimBLE-latest/ext/tinycrypt/include/tinycrypt/ |
H A D | ecc.h | 308 * @param vli IN -- very long integer 482 * @param vli IN -- very long integer 491 * @param vli IN -- very long integer
|
/nrf52832-nimble/packages/NimBLE-latest/ext/tinycrypt/documentation/ |
H A D | tinycrypt.rst | 179 very efficient decryption algorithm that would not otherwise be possible. 250 {95, 94, ..., 64}, {127, 126, ..., 96} for a very-long-integer (vli)
|
/nrf52832-nimble/rt-thread/components/drivers/sensors/ |
H A D | sensor.h | 602 * IMPORTANT NOTE: this sensor type is very different from other types 638 * particular, but not limited to, the accelerometer; which might very well 666 * delay is very large). 685 * particular, but not limited to, the accelerometer; which might very well
|
/nrf52832-nimble/rt-thread/components/utilities/logtrace/ |
H A D | log_trace.h | 121 * level tag in the very beginning.
|
/nrf52832-nimble/rt-thread/components/dfs/filesystems/jffs2/cyg/compress/src/ |
H A D | FAQ | 55 Because we would like to keep zlib as a very small and simple 308 zlib doesn't support encryption. The original PKZIP encryption is very weak
|
/nrf52832-nimble/rt-thread/components/net/uip/apps/webserver/ |
H A D | httpd.c | 9 * The uIP web server is a very simplistic implementation of an HTTP 11 * filesystem, and provides a very small scripting language.
|
/nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/src/core/ |
H A D | memp.c | 80 * This is VERY SLOW but also very helpful. */
|