| /nrf52832-nimble/rt-thread/components/dfs/filesystems/jffs2/cyg/compress/src/ |
| H A D | FAQ | 5 If your question is not there, please check the zlib home page
43 it is not possible to tell whether or not there is more output pending
102 trying to install it, you may want to check if it's already there! If you
103 can #include <zlib.h>, it's there. The -lz option will probably link to it.
137 19. Ok, so why are there two different formats?
225 30. Is there some simpler, easier to read version of inflate I can look at
243 type, but there is no limit to the number of chunks. Note however that the
252 The word "may" appears several times above since there is a 4 GB limit
259 is compiled to use sprintf() or vsprintf(), then there is no protection
263 normally be the case, then there is no vulnerability. The ./configure
[all …]
|
| H A D | algorithm.txt | 29 The hash chains are singly linked. There are no deletions from the
55 but saves time since there are both fewer insertions and fewer searches.
76 table took no time (and if you had infinite memory), then there would only
104 to another similar table for the remaining bits. Again, there are duplicated
106 and there will only be one table look up. (That's whole idea behind data
107 compression in the first place.) For the less frequent long symbols, there
189 There, I think that gives you a picture of what's going on. For inflate, the
|
| H A D | infblock.c | 28 3. There is an implied maximum of 7 bits for the bit length table and
33 5. There is no way of sending zero distance codes--a dummy must be
34 sent if there are none. (History: a pre 2.0 version of PKZIP would
39 6. There are up to 286 literal/length codes. Code 256 represents the
42 cannot be used though, since there is no length base or extra bits
43 defined for them. Similarily, there are up to 30 distance codes.
129 uInt n; /* bytes available there */
|
| /nrf52832-nimble/rt-thread/components/dfs/filesystems/jffs2/cyg/compress/include/ |
| H A D | zlib.h | 87 Bytef *next_out; /* next output byte should be put there */
121 int hcrc; /* true if there was or will be a header crc */
140 zalloc must return Z_NULL if there is not enough memory for the object.
233 deflateInit returns Z_OK if success, Z_MEM_ERROR if there was not
237 msg is set to null if there is no error message. deflateInit does not
253 accordingly. If not all input can be processed (because there is not
270 output buffer because there might be more output pending.
297 pending output is flushed and deflate returns with Z_STREAM_END if there
354 inflateInit returns Z_OK if success, Z_MEM_ERROR if there was not enough
356 version assumed by the caller. msg is set to null if there is no error
[all …]
|
| /nrf52832-nimble/rt-thread/components/dfs/filesystems/jffs2/cyg/compress/ |
| H A D | zlib.h | 87 Bytef *next_out; /* next output byte should be put there */
121 int hcrc; /* true if there was or will be a header crc */
140 zalloc must return Z_NULL if there is not enough memory for the object.
233 deflateInit returns Z_OK if success, Z_MEM_ERROR if there was not
237 msg is set to null if there is no error message. deflateInit does not
253 accordingly. If not all input can be processed (because there is not
270 output buffer because there might be more output pending.
297 pending output is flushed and deflate returns with Z_STREAM_END if there
354 inflateInit returns Z_OK if success, Z_MEM_ERROR if there was not enough
356 version assumed by the caller. msg is set to null if there is no error
[all …]
|
| /nrf52832-nimble/rt-thread/documentation/ |
| H A D | roadmap-2.1.0.md | 3 …There are lot of people ask me what's the features of next version. In fact, I would say, RT-Threa…
7 …rt-thread.org/cloudide, is an online IDE, ah, similar to mbed;-) But hope there are some own chara…
9 …There may be some pits inside. This issue is a big problem, since we chose the open source system,…
|
| H A D | coding_style_en.txt | 41 In every header file, there should be copyright information and Change Log
105 Please use English to comment. There shouldn't be too much comments and the
146 There should be a space before parentheses when it's not a function call. For
159 In expressions, there should be a space between most binary and ternary
|
| /nrf52832-nimble/rt-thread/tools/kconfig-frontends/ |
| H A D | README | 13 However, if there is a bug in the packaging infrastructure, patches are
15 autostuff-based package, I may have done mistakes here and there...
17 As such, there are currently a few known limitations:
33 And there is a stupid bug in libtool that prevents properly linking against
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/host/src/ |
| H A D | ble_hs_stop.c | 64 * If there are no open connections, signals completion of the close procedure.
92 * Event handler. Attempts to terminate the first open connection if there is
96 * If there are no connections, signals completion of the stop procedure.
108 * If there are no connections, signals completion of the stop procedure.
206 * done even if there are no open connections so that the result of the in ble_hs_stop()
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/doc/doxygen/ |
| H A D | main_page.h | 49 * running on target system) or @ref lwip_os (there is an OS running
55 * The user has two possibilities to ensure there is only one
67 * 2) Run lwIP in a mainloop. There is example code here: @ref lwip_nosys.
77 * the TCPIP thread, so there is nothing to consider here.
87 * it is safe to call any @ref callbackstyle_api from there.
|
| /nrf52832-nimble/nordic/nrfx/drivers/include/ |
| H A D | nrfx_twis.h | 90 … /**< If there is no buffer prepared, buf_req flag in the even will be set.
96 … /**< If there is no buffer prepared, buf_req flag in the even will be set.
214 * Function defined if there is needs for dynamically enabling and disabling the peripheral.
325 * @retval false There is no transmission pending.
358 * If this function returns true, it means that there is ongoing output transmission.
362 * @retval true There is ongoing output transmission.
370 * If this function returns true, it means that there is ongoing input transmission.
374 * @retval true There is ongoing input transmission.
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/include/lwip/ |
| H A D | arch.h | 240 * A port to GCC/clang is included in lwIP, if you use these compilers there is nothing to do here.
249 * A port to GCC/clang is included in lwIP, if you use these compilers there is nothing to do here.
258 * A port to GCC/clang is included in lwIP, if you use these compilers there is nothing to do here.
271 * A port to GCC/clang is included in lwIP, if you use these compilers there is nothing to do here.
280 * A port to GCC/clang is included in lwIP, if you use these compilers there is nothing to do here.
289 * A port to GCC/clang is included in lwIP, if you use these compilers there is nothing to do here.
301 * A port to GCC/clang is included in lwIP, if you use these compilers there is nothing to do here.
|
| /nrf52832-nimble/rt-thread/components/vbus/share_hdr/ |
| H A D | vbus_api.h | 38 * central writer thread is waiting. For Linux, it means there are some
41 * Note that we don't record whether there are reading thread blocked. When
42 * there is new data, the other side will always be waked up. */
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/doc/doxygen/ |
| H A D | main_page.h | 84 * in the specification of this API, there might be incompatibilities
136 * running on target system) or @ref lwip_os (there is an OS running
144 * The user has two possibilities to ensure there is only one
156 * 2) Run lwIP in a mainloop. There is example code here: @ref lwip_nosys.
166 * the TCPIP thread, so there is nothing to consider here.
176 * it is safe to call any @ref callbackstyle_api from there.
313 * approach was chosen: there is one main thread running the lwIP core
376 There are C examples given in inet.c or you might want to
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/lwip/ |
| H A D | arch.h | 304 * A port to GCC/clang is included in lwIP, if you use these compilers there is nothing to do here.
313 * A port to GCC/clang is included in lwIP, if you use these compilers there is nothing to do here.
322 * A port to GCC/clang is included in lwIP, if you use these compilers there is nothing to do here.
335 * A port to GCC/clang is included in lwIP, if you use these compilers there is nothing to do here.
344 * A port to GCC/clang is included in lwIP, if you use these compilers there is nothing to do here.
353 * A port to GCC/clang is included in lwIP, if you use these compilers there is nothing to do here.
365 * A port to GCC/clang is included in lwIP, if you use these compilers there is nothing to do here.
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/include/netif/ppp/ |
| H A D | vj.h | 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
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/netif/ppp/ |
| H A D | vj.h | 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
|
| /nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/src/netif/ppp/ |
| H A D | vj.h | 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
|
| /nrf52832-nimble/rt-thread/components/net/freemodbus/port/ |
| H A D | portevent_m.c | 116 * @note There functions will block modbus master poll while execute OS waiting.
138 * @note There functions will block modbus master poll while execute OS waiting.
160 * @note There functions will block modbus master poll while execute OS waiting.
182 * @note There functions will block modbus master poll while execute OS waiting.
|
| /nrf52832-nimble/rt-thread/components/utilities/logtrace/ |
| H A D | log_trace.h | 94 * @return RT_EOK on success. -RT_EFULL if there is no space for registration.
102 * @return RT_NULL if there is no such a session.
116 * "[systick][name]log messages" When there is no session named name, the
|
| /nrf52832-nimble/rt-thread/components/vbus/ |
| H A D | vbus.h | 29 * @datap and @size is recorded in the post queue at least but there is no
33 * However, if you just post static data such as static string, there is no
123 /* There will be a request for each channel. So no need to seperate them so
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/controller/include/controller/ |
| H A D | ble_ll.h | 65 * Another note: BLE_XTAL_SETTLE_TIME should be bsp related (I guess). There
66 * should be a note in there that the converted usecs to ticks value of this
97 * Global Link Layer data object. There is only one Link Layer data object
98 * per controller although there may be many instances of the link layer state
452 /* Tell the Link Layer there has been a data buffer overflow */
455 /* Tell the link layer there has been a hardware error */
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/controller/src/ |
| H A D | ble_ll_sched.c | 59 * a schedule item but there is a current event. We could:
354 * master has to tell the slave how many transmit window offsets there are in ble_ll_sched_master_new()
415 * Are there any allocated periods? If not, set epoch start to earliest in ble_ll_sched_master_new()
584 * master has to tell the slave how many transmit window offsets there are in ble_ll_sched_master_new()
959 * If there is no overlap, we either insert before the 'before' entry in ble_ll_sched_adv_reschedule()
960 * or we insert at the end if there is no before entry. in ble_ll_sched_adv_reschedule()
1239 /* Restart if there is an item on the schedule */ in ble_ll_sched_run()
1250 * If there are not scheduled events this function returns 0; otherwise it
1255 * @return int 0: No events are scheduled 1: there is an upcoming event
1327 * Called to check if there is place for a planned scan req.
[all …]
|
| /nrf52832-nimble/rt-thread/documentation/doxygen/ |
| H A D | kernel.h | 34 * - There are four status in thread management
81 * by priority or FIFO. There are two flags to indicate this mechanism.
112 * There are two methods in dynamic memory heap management, one is used for small memory,
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/host/mesh/ |
| H A D | syscfg.yml | 121 thing to consider is outgoing segmented messages. There must
142 Since there is no single optimal answer, this configuration
189 when setting this option to a higher value. There must be at
191 as there are outgoing segments.
505 if the node operates a security sensitive use case, and there's
|