Searched refs:being (Results 201 – 225 of 345) sorted by relevance
12345678910>>...14
| /Zephyr-latest/subsys/net/l2/ethernet/gptp/ |
| D | Kconfig | 32 source is probed when it is actually needed instead of being
|
| /Zephyr-latest/lib/os/ |
| D | Kconfig.cbprintf | 40 GCC's __udivdi3 helper could end up being pulled into the
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-3.4.rst | 199 the default from being buffered to unbuffered.
234 * On nRF51 and nRF52-based boards, the behavior of the reset reason being
235 provided to :c:func:`sys_reboot` and being set in the GPREGRET register has
747 might wrongly emit a warning about a ``boards`` directory not being found.
1177 * Fixed blocking :c:func:`recv` not being interrupted on socket close.
1178 * Fixed blocking :c:func:`accept` not being interrupted on socket close.
1257 …attempting to mount the disk in a global function caused FAT FS to fail due to not being registere…
1292 header, which is used to indicate the version of the protocol being used.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | core.rst | 106 workqueue, while the stack configuration is being stored.
|
| D | access.rst | 14 a single behavior the node supports, like being a light, a sensor or a
164 while model data is being stored. It is recommended to use this option and the
|
| /Zephyr-latest/kernel/ |
| D | Kconfig | 19 since the main thread cannot pend, it being the only thread in the
583 prevent other threads from being starved. Selecting this removes
748 requirements, ends up being zero, then no system heap will be
767 atomic with respect to the irq_lock being released. That
856 to be good enough for the purpose of being able to configure out
|
| /Zephyr-latest/doc/build/cmake/ |
| D | index.rst | 27 being included in a library target, even application code.
39 being built. Using the keyword ``PUBLIC`` would modify how other
|
| /Zephyr-latest/boards/ezurio/bt610/doc/ |
| D | bt610.rst | 383 For the digital level being applied to be detected, an appropriate output pin
385 powered down when the input state is not being determined. When in use, the
|
| /Zephyr-latest/doc/security/ |
| D | sensor-threat.rst | 249 mandated by the particular service provider being used
270 being reused if they are intercepted. The token shall not be
318 d. **Destruction**. To prevent the device secret from being used to
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/fs_mgmt/ |
| D | Kconfig | 107 from the file being read and generate the output hash/checksum.
|
| /Zephyr-latest/soc/cdns/dc233c/include/ |
| D | xtensa-dc233c.ld | 60 /* The space before exception vectors is not being used.
|
| /Zephyr-latest/drivers/net/ |
| D | Kconfig | 42 is being read to.
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | virtual_memory.rst | 9 the target of Zephyr mainly being embedded systems, virtual memory
|
| /Zephyr-latest/doc/develop/optimizations/ |
| D | tools.rst | 16 about size of symbols and code being used in both RAM and ROM. Additionally,
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_backporting.rst | 13 version of Zephyr (backports), and one for issues that are being fixed only in a previous version.
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_WINDOWS.rst | 61 being brought into A0-A3 (i.e. the new WINDOWBASE) has a set bit
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | cap.rst | 115 Before being able to perform any stream operation, the device must also perform the
277 Before being able to perform any stream operation, the device must also perform the
|
| /Zephyr-latest/doc/contribute/ |
| D | contributor_expectations.rst | 229 any reviews in the PR and should notify the reviewer about their review being
233 expected to block the PR from being merged either by not
|
| /Zephyr-latest/doc/services/logging/ |
| D | cs_stm.rst | 11 access the STM without being aware of each other. Each core has 65536 stimulus ports (identical
19 to STMESP register results in the user data being encoded into MIPI System Trace Protocol v2 (STPv2…
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | setting.rst | 328 symbol without any dependencies will result in the symbol always being
329 assignable. The definition below will result in ``FOO`` always being
|
| D | menuconfig.rst | 71 despite being part of the standard library.
|
| /Zephyr-latest/subsys/bluetooth/audio/ |
| D | Kconfig.bap | 231 being accessed by another thread.
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | message_queues.rst | 34 if space is available. In either case, the size of the data area being sent
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | rbtree.rst | 31 being tracked in the tree. Unlike the list code, the data within an
|
| /Zephyr-latest/doc/services/llext/ |
| D | build.rst | 50 the LLEXT binary being created;
|
12345678910>>...14
