Searched refs:their (Results 176 – 200 of 351) sorted by relevance
12345678910>>...15
| /Zephyr-latest/subsys/logging/ |
| D | Kconfig.formatting | 106 are replaced with their equivalent addresses from the built binary
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | sys_mem_blocks.rst | 48 Due to the use of internal bookkeeping structures and their creation,
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | slist.rst | 94 and "set" primitives for each of head, tail and next pointers on their
|
| /Zephyr-latest/samples/kernel/condition_variables/simple/ |
| D | README.rst | 15 become true. Main thread and the worker thread alternate between their
|
| /Zephyr-latest/boards/hardkernel/odroid_go/doc/ |
| D | index.rst | 212 OpenOCD that are not upstreamed yet. Espressif maintains their own fork of
|
| /Zephyr-latest/doc/build/dts/ |
| D | intro-input-output.rst | 56 their purpose clear. Overlays adapt the base devicetree for different purposes:
|
| /Zephyr-latest/modules/mbedtls/ |
| D | CMakeLists.txt | 253 # included the required directories for mbedtls in their projects.
|
| /Zephyr-latest/ |
| D | CODE_OF_CONDUCT.md | 35 without their explicit permission
|
| /Zephyr-latest/boards/nxp/lpcxpresso54114/doc/ |
| D | index.rst | 10 engineers to develop their applications from initial evaluation to final
|
| /Zephyr-latest/doc/develop/west/ |
| D | manifest.rst | 21 West's view of the repositories in a :term:`west workspace`, and their
97 key. Any other keys and their contents are ignored (west v0.5 also required a
118 below, projects can also specify their complete fetch URLs.)
132 The ``remotes`` keys and their usage are in the following table.
220 The available project keys and their usage are in the following table.
355 The available ``defaults`` keys and their usage are in the following table.
395 The available ``self`` keys and their usage are in the following table.
617 contain these characters elsewhere in their names. For example, ``foo-bar`` and
791 Both ``foo`` and ``bar`` are inactive, because all of their groups are
2091 from Git at the latest ``manifest-rev`` revisions in their projects. These
|
| /Zephyr-latest/drivers/modem/ |
| D | Kconfig | 151 modem "sockets" throughout their lifecycle (from the initial offload
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu_srv.rst | 24 firmware update capabilities could have three entries in the firmware image list, each with their
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | coap_server.rst | 29 their respective linker sections. If you would have a service ``my_service`` it has to be
|
| /Zephyr-latest/boards/seeed/xiao_esp32c6/doc/ |
| D | index.rst | 205 OpenOCD that are not upstreamed yet. Espressif maintains their own fork of
|
| /Zephyr-latest/boards/st/stm32u5a9j_dk/doc/ |
| D | index.rst | 18 enhance their application development by an evaluation of all the peripherals
|
| /Zephyr-latest/boards/heltec/heltec_wifi_lora32_v2/doc/ |
| D | index.rst | 162 OpenOCD that are not upstreamed yet. Espressif maintains their own fork of
|
| /Zephyr-latest/boards/others/esp32c3_supermini/doc/ |
| D | index.rst | 219 OpenOCD that are not upstreamed yet. Espressif maintains their own fork of
|
| /Zephyr-latest/subsys/testsuite/ |
| D | Kconfig | 108 tag in their testcase.yaml file.
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 50 <modules>` maintained by their respective vendors. This means that in order to
215 support from their maintainers. This is required to maintain project control
|
| /Zephyr-latest/doc/build/cmake/ |
| D | index.rst | 72 scripts also do some processing of their own, which is explained here.
155 together to bind potential system call functions with their
|
| /Zephyr-latest/boards/qemu/x86/ |
| D | qemu_x86_tiny.ld | 599 * to their corresponding virtual addresses.
602 * their virtual addresses. This provides a simple and
|
| /Zephyr-latest/doc/kernel/services/smp/ |
| D | smp.rst | 56 architectures to define their own for performance reasons.
80 SMP systems with identical semantics to their legacy versions. They
347 to schedule, and follow through with their own :c:func:`arch_switch` or
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-4.0.rst | 104 * ``zcbor_simple_*()`` functions have been removed to avoid confusion about their use.
127 ``microchip,mcp230xx`` and ``microchip,mcp23sxx`` should change their devicetree ``compatible``
131 their driver API, users of these devices should ensure they pass appropriate values to
|
| /Zephyr-latest/doc/develop/flash_debug/ |
| D | probes.rst | 25 Several hardware vendors have their own branded onboard debug probe
33 that communicate with their respective debug host tools. For example, an
323 boards to support their external flash memories, whereas generic firmwares are
|
| /Zephyr-latest/subsys/bluetooth/ |
| D | Kconfig | 254 can set their own. Note that the controller's Company Identifier is
|
12345678910>>...15
