Searched refs:these (Results 351 – 375 of 642) sorted by relevance
1...<<11121314151617181920>>...26
/Zephyr-latest/doc/connectivity/networking/api/ |
D | capture.rst | 50 For example, in the sample capture application, these network interfaces
|
/Zephyr-latest/doc/develop/tools/ |
D | vscode.rst | 102 …Please be aware that these extensions might not all have the same level of quality and maintenance.
|
/Zephyr-latest/kernel/ |
D | CMakeLists.txt | 199 # above these 2 files.
|
D | Kconfig.obj_core | 118 system objects into the object core framework. As these are internal
|
/Zephyr-latest/samples/net/cloud/mqtt_azure/ |
D | README.rst | 53 You'll also need to set these Kconfig options if you're running
|
/Zephyr-latest/drivers/espi/ |
D | Kconfig.npcx | 151 entry as EC needs to maintain these pins' states per request.
|
/Zephyr-latest/tests/kernel/context/ |
D | README.txt | 52 - Use these routines to disable and enable timer interrupts so that they can
|
/Zephyr-latest/tests/drivers/build_all/dac/ |
D | app.overlay | 9 * with real-world devicetree nodes, to allow these tests to run on
|
/Zephyr-latest/samples/drivers/ipm/ipm_ivshmem/ |
D | README.rst | 55 and create them, these folders will receive the output of Zephyr west commands:
|
/Zephyr-latest/include/zephyr/arch/riscv/common/ |
D | linker.ld | 313 * Since these immediate offsets are signed, place gp 0x800 past the 437 /* Output section descriptions are needed for these sections to suppress
|
/Zephyr-latest/doc/connectivity/networking/ |
D | overview.rst | 119 that no automatic IP routing functionality is provided between these 143 Additionally these network technologies (link layers) are supported in
|
/Zephyr-latest/doc/services/llext/ |
D | build.rst | 5 into a running Zephyr application. When building these extensions, it's very 208 None of these flags are included in the above lists.
|
/Zephyr-latest/cmake/modules/ |
D | kernel.cmake | 84 # paths can be changed, e.g. to flash signed versions of these files 184 # If we are using a suitable ethernet driver inside qemu, then these options
|
/Zephyr-latest/boards/native/nrf_bsim/doc/ |
D | nrf52_bsim.rst | 42 and will use the same drivers as the nrf52 dk targets for these. 95 You can add these two lines to your ``~/.zephyrrc`` file, or to your shell
|
/Zephyr-latest/boards/toradex/verdin_imx8mm/doc/ |
D | index.rst | 138 Stack Pointer, and get the M4 out of reset. The A53 can perform these steps at the 218 To load and start a firmware use these commands:
|
/Zephyr-latest/boards/96boards/meerkat96/doc/ |
D | index.rst | 155 Stack Pointer, and get the M4 out of reset. The A7 can perform these steps at 290 With these mechanisms, applications for the ``96b_meerkat96`` board
|
/Zephyr-latest/drivers/sensor/maxim/max30101/ |
D | Kconfig | 87 pulse/conversion per active LED channel. In SpO2 mode, these means
|
/Zephyr-latest/boards/pine64/pinetime_devkit0/doc/ |
D | index.rst | 132 Only a few devs have soldered to these pins, most just use friction to make
|
/Zephyr-latest/boards/infineon/cy8cproto_063_ble/doc/ |
D | index.rst | 66 …ogramming Tools`_ packages include Infineon OpenOCD. Installing either of these packages will also…
|
/Zephyr-latest/soc/sensry/ganymed/sy1xx/common/ |
D | linker.ld | 250 * Pulpino toolchains emit these sections; we don't care about them,
|
/Zephyr-latest/boards/weact/stm32g431_core/doc/ |
D | index.rst | 19 After these modifications have been made, PA9, PA10, PB2, PB4, and PB6 should be
|
/Zephyr-latest/doc/services/storage/flash_map/ |
D | flash_map.rst | 45 DTS node label using :c:macro:`FIXED_PARTITION_ID()`; these labels are obtained
|
/Zephyr-latest/boards/nxp/rd_rw612_bga/ |
D | rd_rw612_bga.dtsi | 250 * Similar to the flexio connection, these pins are not
|
/Zephyr-latest/doc/services/net_buf/ |
D | index.rst | 65 decoding data in the buffers. To fully understand these helpers it's
|
/Zephyr-latest/dts/arm/st/h7/ |
D | stm32h723.dtsi | 47 * ADC, so we redefine the resolution for these devices.
|
1...<<11121314151617181920>>...26