Searched refs:locations (Results 26 – 50 of 55) sorted by relevance
123
| /Zephyr-latest/doc/build/dts/ |
| D | intro-input-output.rst | 66 certain locations. It is also possible to explicitly list the overlays to
|
| D | intro-syntax-structure.rst | 56 Devicetree nodes have *paths* identifying their locations in the tree. Like
|
| D | howtos.rst | 40 CMake prints the input and output file locations like this:
|
| /Zephyr-latest/doc/kernel/ |
| D | code-relocation.rst | 41 locations. This is due to the behavior of the linker. The linker will only
|
| /Zephyr-latest/doc/build/snippets/ |
| D | writing.rst | 90 locations.
|
| /Zephyr-latest/drivers/i2c/ |
| D | Kconfig | 118 # overridden (by defining symbols in multiple locations)
|
| /Zephyr-latest/doc/develop/west/ |
| D | basics.rst | 97 the locations of all the projects in the workspace, so any code they contain
|
| D | workspaces.rst | 136 Project locations
|
| D | release-notes.rst | 271 options from any or all of these locations.
|
| /Zephyr-latest/ |
| D | Kconfig.zephyr | 564 When enabled, locations of tokens across macro expansions will be
756 relocatable, and cannot be placed at specific locations in memory.
758 appropriate locations at startup, clear any zero-filled (BSS, etc...)
959 This saves some memory, stops leaking user locations in binaries, makes
|
| D | CMakeLists.txt | 62 # Some generators require that memory locations has been fixed, thus those are
525 # application code. This saves some memory, stops leaking user locations
|
| /Zephyr-latest/dts/arm/microchip/ |
| D | mec5.dtsi | 619 * to one of the 4-byte locations.
|
| /Zephyr-latest/doc/security/ |
| D | sensor-threat.rst | 137 In addition to assets, the threat model also considers the locations
303 all locations outside of the device once it has been programmed
|
| /Zephyr-latest/doc/develop/test/ |
| D | pytest.rst | 80 Pytest scans the given locations looking for tests, following its default
|
| /Zephyr-latest/boards/udoo/udoo_neo_full/doc/ |
| D | index.rst | 230 M4 core using hardcoded shared memory locations. The utility writes a flag which
|
| /Zephyr-latest/cmake/modules/ |
| D | dts.cmake | 55 # - DTS_ROOT_BINDINGS is set to a ;-list of locations where DT
|
| /Zephyr-latest/doc/develop/debug/ |
| D | index.rst | 115 :file:`.gdbinit`, but you can configure GDB to load from other locations,
|
| /Zephyr-latest/doc/develop/ |
| D | beyond-GSG.rst | 95 of the :ref:`recommended locations <toolchain_zephyr_sdk_bundle_variables>`,
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | tips.rst | 788 defining a symbol in multiple locations and wanting to override e.g. a
862 For a symbol defined in multiple locations (e.g., in a ``Kconfig.defconfig``
|
| /Zephyr-latest/arch/ |
| D | Kconfig | 9 # overridden (by defining symbols in multiple locations)
1035 point to the same cached/uncached memory at different locations.
|
| /Zephyr-latest/doc/project/ |
| D | project_roles.rst | 236 geographically distributed across multiple locations and
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.9.rst | 249 …1`` - Move all board pinmux code from drivers/pinmux/stm32 to the corresponding board/soc locations
|
| D | release-notes-1.7.rst | 231 * ``ZEP-931`` - Finalize kernel file naming & locations
|
| /Zephyr-latest/doc/contribute/documentation/ |
| D | guidelines.rst | 613 Target locations in a document are defined with a label directive::
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 120 | :ref:`freestanding | other locations |
|
123
