Home
last modified time | relevance | path

Searched full:are (Results 1 – 25 of 1567) sorted by relevance

12345678910>>...63

/nrf52832-nimble/rt-thread/components/dfs/filesystems/jffs2/cyg/compress/src/
H A Dalgorithm.txt7 length). Distances are limited to 32K bytes, and lengths are limited
13 Literals or match lengths are compressed with one Huffman tree, and
14 match distances are compressed with another tree. The trees are stored
21 Duplicated strings are found using a hash table. All input strings of
22 length 3 are inserted in the hash table. A hash index is computed for
24 strings in the chain are compared with the current input string, and
27 The hash chains are searched starting with the most recent strings, to
29 The hash chains are singly linked. There are no deletions from the
30 hash chains, the algorithm simply discards matches that are too old.
32 To avoid a worst-case situation, very long hash chains are arbitrarily
[all …]
H A Dinftrees.c22 The code lengths are lens[0..codes-1]. The result starts at *table,
23 whose indices are 0..2^bits-1. work is a writable array of at least
77 code lengths are lens[0..codes-1]. Each length corresponds to the
81 for the first code of the shortest length, and the codes are integer
82 increments for the same length, and zeros are appended as the length
83 increases. For the deflate format, these bits are stored backwards
85 decoding tables are built in the large loop below, the integer codes
86 are incremented backwards.
89 lens[] are in the range 0..MAXBITS. The caller must assure this.
93 The codes are sorted by computing a count of codes for each length,
[all …]
/nrf52832-nimble/rt-thread/components/net/uip/doc/
H A Dpt-doc.txt4 Protothreads are a type of lightweight stackless threads designed for
10 Protothreads are a extremely lightweight, stackless type of threads
33 blocking call, <b>local variables are not preserved when the
65 convenience functions are built: reversed condition blocking:
81 Protothreads are a extremely lightweight, stackless threads that
95 protothreads are very lightweight: a protothread does not require its
100 memory per protothread. Moreover, protothreads are implemented in pure
111 Protothreads are similar to asymmetric co-routines. The main
113 co-routine, whereas protothreads are stackless. The most similar
114 mechanism to protothreads are Python generators. These are also
[all …]
H A Duip-doc.txt55 are very rarely used in such situations. Many of those mechanisms are
71 application". Lower layer protocols are often implemented in hardware
72 or firmware and will be referred to as "the network device" that are
77 segment is sent in its own IP packet. The IP packets are sent out on
83 packets by the router. If possible, the size of the TCP segments are
107 are implemented. However, in order to reduce code size, we have
111 connections. Since there are only very few applications that make use
130 Periodic timeouts are used to drive TCP mechanisms that depend on
143 implementations are given as part of the uIP distribution.
198 Ethernet controllers have on-chip buffers that are large enough to
[all …]
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/core/
H A Dsys.c12 * are permitted provided that the following conditions are met:
24 * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
65 * must define are listed below the sys_arch description.
67 * Since lwIP 1.4.0, semaphore, mutexes and mailbox functions are prototyped in a way that
83 * Semaphores are represented by the type "sys_sem_t" which is typedef'd
84 * in the sys_arch.h file. Mailboxes are equivalently represented by the
85 * type "sys_mbox_t". Mutexes are represented by the type "sys_mutex_t".
86 * lwIP does not place any restrictions on how these types are represented
91 * Mutexes are recommended to correctly handle priority inversion,
108 * and interrupts are under your control:
[all …]
H A Ddef.c5 * These are reference implementations of the byte swapping functions.
13 * Note lwip_ntohs() and lwip_ntohl() are merely references to the htonx counterparts.
25 * These options cannot be \#defined in lwipopts.h since they are not options
34 * are permitted provided that the following conditions are met:
46 * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
138 /* characters are not equal an one is in the alphabet range: in lwip_stricmp()
147 /* characters are not equal but none is in the alphabet range */ in lwip_stricmp()
173 /* characters are not equal an one is in the alphabet range: in lwip_strnicmp()
182 /* characters are not equal but none is in the alphabet range */ in lwip_strnicmp()
/nrf52832-nimble/rt-thread/tools/kconfig-frontends/docs/
H A Dkconfig-language.txt20 Every entry has its own dependencies. These dependencies are used
48 A menu entry can have a number of attributes. Not all of them are
52 Every config option must have a type. There are only two basic types:
53 tristate and string; the other types are based on these two. The type
55 are equivalent:
69 default values are visible, only the first defined one is active.
70 Default values are not limited to the menu entry where they are
87 dependencies are defined, they are connected with '&&'. Dependencies
88 are applied to all other options within this menu entry (which also
89 accept an "if" expression), so these two examples are equivalent:
[all …]
/nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/doc/
H A Dsnmp_agent.txt26 The groups EGP, CMOT and transmission are disabled by default.
28 Most mib-2 objects are not writable except:
41 All routes are considered to be up (U).
48 The packet decoding and encoding routines are designed
50 SNMP requirement of 484 octets are supported if the
51 PBUF_POOL_SIZE and IP_REASS_BUFSIZE are set to match your
124 ALL OBJECT IDENTIFIERS LIVING UNDER THIS ID ARE ASSIGNED BY THE lwIP
164 Object identifiers from incoming requests are checked
166 or are expanded(*) for GetNext requests with short
178 These trees are updated by e.g. the etharp code
[all …]
H A Dsys_arch.txt22 must define are listed below the sys_arch description.
25 kinds. Mailboxes are used for message passing and can be implemented
32 Semaphores are represented by the type "sys_sem_t" which is typedef'd
33 in the sys_arch.h file. Mailboxes are equivalently represented by the
35 sys_sem_t or sys_mbox_t are represented internally.
37 Since lwIP 1.4.0, semaphore and mailbox functions are prototyped in a way that
100 in mailboxes are pointers. You have to define macros "_MBOX_SIZE"
109 Deallocates a mailbox. If there are messages still present in the
133 The return values are the same as for the sys_arch_sem_wait() function:
167 If threads are supported by the underlying operating system and if
[all …]
/nrf52832-nimble/rt-thread/documentation/
H A DDoxyfile69 # The default language is English, other supported languages are:
80 # include brief member descriptions after the members that are listed in
88 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
98 # If left blank, the following values are used ("$name" is automatically
115 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
148 # are normally passed to the compiler using the -I flag.
217 # For instance, some of the names that are used will be different. The list
249 # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
273 # For Microsoft's IDL there are propget and propput attributes to indicate getter
276 # documentation. This will only work if the methods are indeed getting or
[all …]
/nrf52832-nimble/rt-thread/components/drivers/sensors/
H A Dsensor.h77 * the axis are not swapped when the device's screen orientation changes.
109 * events are lost.
112 * suspend mode -- it's just that the data it returns are lost. As soon as
123 * There are notable exceptions to this behavior, which are sensor-dependent
130 * wake-up: no this sensor shall not wake-up the SoC, events are dropped
138 * measures are reported. All types are defined below.
142 * sensor types are specific to an OEM and can't be exposed in the SDK.
155 * Many sensor types are or can be implemented as virtual sensors from
173 * Currently there are four trigger modes defined:
175 * continuous: events are reported at a constant rate defined by setDelay().
[all …]
/nrf52832-nimble/rt-thread/documentation/doxygen/
H A Dkernel.h8 * The Kernel APIs are the core APIs of RT-Thread, which supports the following
26 * RT-Thread operating system supports multitask systems, which are based on thread
29 * - 8/32/256 priority levels are supported, in which 0 is the highest and 7/31/255 the lowest.
31 * - Threads running at same priority level are supported. The shared time-slice
34 * - There are four status in thread management
81 * by priority or FIFO. There are two flags to indicate this mechanism.
108 * or waiting for sometime to return, which are determined by a timeout parameter).
112 * There are two methods in dynamic memory heap management, one is used for small memory,
139 * The hooks are a series of routines, which are invoked in some special checkpoints.
/nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/include/netif/ppp/
H A Dvj.h9 * Redistribution and use in source and binary forms are permitted
10 * provided that the above copyright notice and this paragraph are
44 * the compressed packet. The next two octets are the TCP checksum
45 * from the original datagram. The next 0 to 15 octets are
47 * (there may be no changes and there are two special cases where
50 * There are 5 numbers which can change (they are always inserted
65 * The top nibble of the first octet is the packet type. There are
74 * three bits are actual packet type. For backward compatibility
75 * and in the interest of conserving bits, numbers are chosen so the
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/netif/ppp/
H A Dvj.h9 * Redistribution and use in source and binary forms are permitted
10 * provided that the above copyright notice and this paragraph are
48 * the compressed packet. The next two octets are the TCP checksum
49 * from the original datagram. The next 0 to 15 octets are
51 * (there may be no changes and there are two special cases where
54 * There are 5 numbers which can change (they are always inserted
69 * The top nibble of the first octet is the packet type. There are
78 * three bits are actual packet type. For backward compatibility
79 * and in the interest of conserving bits, numbers are chosen so the
/nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/src/netif/ppp/
H A Dvj.h9 * Redistribution and use in source and binary forms are permitted
10 * provided that the above copyright notice and this paragraph are
41 * the compressed packet. The next two octets are the TCP checksum
42 * from the original datagram. The next 0 to 15 octets are
44 * (there may be no changes and there are two special cases where
47 * There are 5 numbers which can change (they are always inserted
62 * The top nibble of the first octet is the packet type. There are
71 * three bits are actual packet type. For backward compatibility
72 * and in the interest of conserving bits, numbers are chosen so the
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/doc/doxygen/
H A Dlwip.Doxyfile30 # double-quotes, unless you are using Doxywizard) that should identify the
84 # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,
97 # descriptions after the members that are listed in the file and class
106 # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
117 # following values are used ($name is automatically replaced with the name of
133 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
171 # specify the list of include paths that are normally passed to the compiler
206 # Note that setting this tag to YES also means that rational rose comments are
251 # instance, some of the names that are used will be different. The list of all
292 # the files are not read by doxygen.
[all …]
H A Dlwip.Doxyfile.cmake.in30 # double-quotes, unless you are using Doxywizard) that should identify the
84 # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,
97 # descriptions after the members that are listed in the file and class
106 # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
117 # following values are used ($name is automatically replaced with the name of
133 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
171 # specify the list of include paths that are normally passed to the compiler
206 # Note that setting this tag to YES also means that rational rose comments are
251 # instance, some of the names that are used will be different. The list of all
292 # the files are not read by doxygen.
[all …]
/nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/doc/doxygen/
H A Dlwip.Doxyfile30 # double-quotes, unless you are using Doxywizard) that should identify the
84 # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,
97 # descriptions after the members that are listed in the file and class
106 # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
117 # following values are used ($name is automatically replaced with the name of
133 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
171 # specify the list of include paths that are normally passed to the compiler
206 # Note that setting this tag to YES also means that rational rose comments are
251 # instance, some of the names that are used will be different. The list of all
292 # the files are not read by doxygen.
[all …]
/nrf52832-nimble/packages/NimBLE-latest/docs/
H A Ddoxygen.xml48 # double-quotes, unless you are using Doxywizard) that should identify the
102 # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,
115 # descriptions after the members that are listed in the file and class
124 # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
135 # following values are used ($name is automatically replaced with the name of
141 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
179 # specify the list of include paths that are normally passed to the compiler
214 # Note that setting this tag to YES also means that rational rose comments are
259 # instance, some of the names that are used will be different. The list of all
300 # the files are not read by doxygen.
[all …]
/nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/core/
H A Ddef.c5 * These are reference implementations of the byte swapping functions.
13 * Note lwip_ntohs() and lwip_ntohl() are merely references to the htonx counterparts.
25 * These options cannot be \#defined in lwipopts.h since they are not options
34 * are permitted provided that the following conditions are met:
46 * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
138 /* characters are not equal an one is in the alphabet range: in lwip_stricmp()
147 /* characters are not equal but none is in the alphabet range */ in lwip_stricmp()
173 /* characters are not equal an one is in the alphabet range: in lwip_strnicmp()
182 /* characters are not equal but none is in the alphabet range */ in lwip_strnicmp()
/nrf52832-nimble/rt-thread/examples/test/
H A Ddhry.h27 * In this C version, the following C library functions are used:
31 * are used for execution time measurement. For measurements
95 * are not executed. The intention is that optimizing compilers
98 * that are executed within the measurement loop have NOT been
111 * All changes within the measurement loop are described
117 * changed, there are still cases where optimizing compilers
120 * Users of the benchmark are advised to check code listings
132 * Defines: The following "Defines" are possible:
137 * - for local variables, if they are used (dynamically)
139 * - for parameters if they are used (dynamically)
[all …]
/nrf52832-nimble/nordic/nrfx/drivers/include/
H A Dnrfx_nfct.h6 * modification, are permitted provided that the following conditions are met:
22 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
68 * @details These states are substates of the @ref NRFX_NFCT_STATE_ACTIVATED state.
195 …orwarded to the upper layer by using @ref nrfx_nfct_evt_id_t. By default, no events are enabled. */
219 * After this function completes, NFC readers are able to detect the tag.
226 * After this function returns, NFC readers are no longer able to connect
337 * If you are using the nRF52832 chip, the workarounds for the following anomalies are applied:
345 …* If you are using the nRF52840 chip, rev. Engineering A, the workarounds for the following anomal…
346 * are applied:
351 …* If you are using the nRF52840 chip, rev. 1, or rev. Engineering B or C, the workarounds for the …
[all …]
H A Dnrfx_i2s.h6 * modification, are permitted provided that the following conditions are met:
22 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
111 /**< The application should provide buffers that are to be used in the next
113 * be done before the currently used buffers are completely processed
140 * buffers are used for the second time) and no buffers
142 * Both pointers in this structure are NULL when the
185 * directions are enabled) is specified in 32-bit words. One 32-bit memory
197 * (buffers for all consecutive parts are provided
202 * Currently, no additional flags are available.
207 * @retval NRFX_ERROR_INVALID_ADDR If the provided buffers are not placed
/nrf52832-nimble/rt-thread/tools/
H A Dkconfiglib.py43 The targets added by the Makefile patch are described in the following
81 The make targets are only needed to pick up environment variables exported from
85 These variables are referenced as of writing (Linux 4.18), together with sample
126 condition on the prompt. Symbols without prompts are never visible, so setting
129 symbols are normal within a .config file, so no similar warning will be printed
132 Dependencies from parents and 'if'/'depends on' are propagated to properties,
133 including prompts, so these two configurations are logically equivalent:
167 'default' properties are independent of the visibility, though a 'default' will
169 'default' properties are used if the symbol is not visible or has no user
172 Symbols with no user value (or that have a user value but are not visible) and
[all …]
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/lwip/apps/
H A Dhttpd_opts.h11 * are permitted provided that the following conditions are met:
23 * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
71 * (@ref tCGIHandler) for all URLs that are found. fs_open is called first
89 * All files with one of these extensions are parsed when sent.
114 * Default is 1 (file extensions are checked using the g_pcSSIExtensions array)
135 * arguments indicating a counter for insert string that are too long to be
143 * ATTENTION: tags longer than this are ignored, not truncated!
166 * at runtime. Default is off: HTTP headers are then created statically
271 are received - otherwise the input pbuf is used directly) */
320 /** Default: Tags are sent from struct http_state and are therefore volatile */
[all …]

12345678910>>...63