Searched refs:very (Results 101 – 125 of 165) sorted by relevance
1234567
5 into a running Zephyr application. When building these extensions, it's very
154 very important in terms of safety. On the one hand, this specifies and describes in detail and on a200 very high level, and thus it can be determined which functionalities are safety-relevant and can be
90 # CMake's 'project' concept has proven to not be very useful for Zephyr
78 Systems with very large amounts of memory (such as 512M or more)
1702 very very||very
26 read operation is very fast. The expectation is that very sensitive
104 The page-tables-specified-in-virtual-memory trick works very well in188 6. Disable the initial/way6 instruction TLBs second. The very next
159 which can be very useful if the UART (through USB CDC ACM) is already being used for
35 operations etc. This is very good for system stability.
40 the very space-optimized but limited formatter used for :c:func:`printk`
62 # An exclusion list with the very option means only allow once
209 should be treated as a very serious condition impacting the health of the
195 one CPU cluster can be very different from another CPU cluster, therefore each
151 sample. This is a very simple algorithm which ranks data pages on whether
283 Note that if you try to send the very same image that is already flashed in
12 writing and executing via an LwM2M server in a very lightweight environment.
58 configuration supports the hardware features below. Another very similar
54 configuration supports the hardware features below. Another very similar
91 :c:func:`irq_lock` are not simply invoking a very short (often ~1182 interprocessor interrupt. The current framework is very simple: the
16 The polling API's main function is :c:func:`k_poll`, which is very similar
78 Zephyr's very own BLE Host and Controller, users of the Zephyr Controller can
77 # hostap debug is very verbose and despite large log buffer sizes
156 However, this operation is very time consuming and needs to browse all valid ATEs in all sectors405 ATEs and smaller header ATEs). Erasing flash in NVS is also very fast and do not require an
215 by a user thread. This is very uncommon, typically only for kernel objects that
6 The devicetree concept of a *phandle* is very similar to pointers in
