Searched refs:rely (Results 1 – 25 of 58) sorted by relevance
123
| /Zephyr-latest/soc/openisa/rv32m1/ |
| D | CMakeLists.txt | 5 # Let's rely on `-march` being generated by the CMake script based on which `CONFIG_RISCV_ISA_EXT_*`
|
| /Zephyr-latest/cmake/compiler/arcmwdt/ |
| D | target.cmake | 29 # we rely on default MWDT header locations and don't manually specify headers directories.
40 # We can't rely on these functions presence if we don't use MWDT libc.
|
| D | compiler_flags.cmake | 202 # We rely on the default C/C++ include locations which are provided by MWDT if we do build with
|
| /Zephyr-latest/arch/x86/core/ |
| D | ia32.cmake | 6 # We rely on GAS for assembling, so don't use the integrated assembler
|
| /Zephyr-latest/drivers/tee/optee/ |
| D | Kconfig | 10 of the hardware isolation and rely to ARM TrustZone technology.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | cfg.rst | 13 cases, the mesh node can't rely on the Configuration Client to detect or determine
|
| /Zephyr-latest/boards/qemu/arc/ |
| D | board.cmake | 24 # Let's rely on the QEMU defaults instead of specifying exact board name,
|
| /Zephyr-latest/boards/mediatek/mt8196/ |
| D | mt8196_adsp.dts | 54 * rely on such a configuration.
|
| /Zephyr-latest/arch/x86/zefi/ |
| D | README.txt | 56 So we can only rely on the C file's internal linkage, which is done
57 via the x86_64 RIP-relative addressing mode and doesn't rely on any
|
| /Zephyr-latest/doc/develop/languages/c/ |
| D | minimal_libc.rst | 11 It is very low footprint and is suitable for projects that do not rely on less
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.x86 | 62 then this choice will rely on the TSC as time source and the
|
| /Zephyr-latest/doc/develop/west/ |
| D | sign.rst | 15 rimage configuration uses an approach that does not rely on Kconfig or CMake
|
| /Zephyr-latest/doc/services/portability/posix/implementation/ |
| D | index.rst | 37 - When the POSIX API and another Zephyr subsystem both rely on a feature, the implementation of
|
| /Zephyr-latest/samples/modules/tflite-micro/hello_world/ |
| D | README.rst | 34 The sample should work on most boards since it does not rely
|
| /Zephyr-latest/samples/net/telnet/ |
| D | README.rst | 70 <frdm_k64f>` network configuration for IPv4 will rely on DHCPv4. You cad modify
|
| /Zephyr-latest/subsys/pm/ |
| D | Kconfig | 110 only rely on Runtime PM to manage the devices power states.
|
| /Zephyr-latest/samples/ |
| D | sample_definition_and_criteria.rst | 64 file and should be operational on all supported platforms. Do not rely on the
|
| /Zephyr-latest/scripts/ci/es_upload/ |
| D | README.md | 14 by other tools, or rely on default data mapping with potential type misalignments.
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig | 59 disabled, UART controllers rely on UART driver's
|
| /Zephyr-latest/soc/espressif/common/ |
| D | Kconfig.esptool | 23 3. Please do not rely on this option when you are pretty sure that you are using Octal flash,
|
| /Zephyr-latest/doc/develop/languages/cpp/ |
| D | index.rst | 87 not rely on the Standard Template Library (STL) components.
211 C++20. Other standard revisions may vary. In doubt, do not rely on
|
| /Zephyr-latest/doc/develop/ |
| D | env_vars.rst | 221 will try to locate those programs automatically, but may rely on additional
|
| /Zephyr-latest/doc/build/dts/ |
| D | api-usage.rst | 347 rely on :ref:`instance identifiers <dt-node-identifiers>`.
383 While the :file:`zephyr/devicetree.h` API is not generated, it does rely on a
|
| /Zephyr-latest/cmake/modules/ |
| D | kernel.cmake | 93 # Zephyr therefore tries to rely as little as possible on project()
|
| /Zephyr-latest/doc/kernel/drivers/ |
| D | index.rst | 350 Used for devices that have no dependencies, such as those that rely
358 Used for devices that rely on the initialization of devices initialized
|
123
