Searched full:those (Results 1 – 25 of 564) sorted by relevance
12345678910>>...23
| /Zephyr-latest/tests/arch/arc/arc_vpx_lock/ |
| D | README.txt | 7 lock/unlock mechanism does not technically require those registers to be
9 the test does not actually access those VPX registers.
|
| /Zephyr-latest/cmake/linker/ |
| D | linker_libraries_template.cmake | 6 # It is the responsibility of the linker infrastructure to use those properties to specify the
7 # correct placement of those libraries for correct link order.
|
| /Zephyr-latest/doc/develop/west/ |
| D | without-west.rst | 46 maintain those additional repositories, adding new ones as necessary
75 west, you will need to download and place those blobs in the right places
85 those targets will fail. You can of course still flash and debug using
86 any :ref:`flash-debug-host-tools` which work for your board (and which those
|
| /Zephyr-latest/tests/bluetooth/tester/ |
| D | hci_ipc.conf | 4 # Those have to be the same as in the controller (hci_ipc)
|
| /Zephyr-latest/tests/subsys/ipc/pbuf/ |
| D | testcase.yaml | 3 # For native(POSIX arch) targets, let's skip those which do not produce an executable
|
| /Zephyr-latest/cmake/linker/armlink/ |
| D | target.cmake | 97 # Thus silence those two warnings.
103 # __kernel_ram_x symbols, but nothing will go in those section, so silence
107 # Use of '.gnu.linkonce' sections. Those are used by ld, and # supported by armlink, albeit
111 # Wildcard matching of keep sections, Those are needed for gnu ld, and thus we inherit the same
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | dma.rst | 29 DMA channels require mutating shared registers, those register updates should be wrapped in a spin
39 transfer descriptors then those should be setup in a way that does not break the promise of
50 A diagram, showing those expected possible state transitions and their API calls is provided here
|
| /Zephyr-latest/samples/boards/nordic/nrfx_prs/ |
| D | prj.conf | 2 # between those peripherals, as they share the same ID and hence cannot be used
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_mac.rst | 15 macOS will not let you execute those from the Terminal by default. In order to
29 Homebrew, since those are automatically un-quarantined by ``brew`` itself. This
|
| /Zephyr-latest/dts/bindings/phy/ |
| D | phy-controller.yaml | 13 Number of cells in a PHY provider. The meaning those
|
| /Zephyr-latest/tests/bsim/bluetooth/host/misc/hfc/ |
| D | prj.conf | 23 # FIXME: enable those to see a bug
|
| /Zephyr-latest/scripts/native_simulator/common/src/include/ |
| D | nsi_cpu_if.h | 31 * direct the linker to keep those symbols even when doing its linking with garbage collection.
32 * It is also be possible for the embedded SW to require the linker to keep those
104 * When the runner HW models use them and for what is up to those
|
| /Zephyr-latest/drivers/gnss/ |
| D | Kconfig.generic | 28 device is actually tracking, just how many of those can be reported
|
| D | Kconfig.luatos_air530z | 26 the device is actually tracking, just how many of those can
|
| D | Kconfig.u_blox_m8 | 29 device is actually tracking, just how many of those can be reported
|
| /Zephyr-latest/samples/bluetooth/direction_finding_central/boards/ |
| D | nrf5340dk_nrf5340_cpuapp.overlay | 10 * Note: Pay attention to assign the same GPIO pins as those provided in
|
| /Zephyr-latest/samples/bluetooth/direction_finding_connectionless_rx/boards/ |
| D | nrf5340dk_nrf5340_cpuapp.overlay | 10 * Note: Pay attention to assign the same GPIO pins as those provided in
|
| /Zephyr-latest/samples/bluetooth/direction_finding_peripheral/boards/ |
| D | nrf5340dk_nrf5340_cpuapp.overlay | 10 * Note: Pay attention to assign the same GPIO pins as those provided in
|
| /Zephyr-latest/samples/bluetooth/direction_finding_connectionless_tx/boards/ |
| D | nrf5340dk_nrf5340_cpuapp.overlay | 10 * Note: Pay attention to assign the same GPIO pins as those provided in
|
| /Zephyr-latest/tests/subsys/logging/dictionary/ |
| D | testcase.yaml | 4 # So platform_allow list needs to limit to those platforms.
|
| /Zephyr-latest/samples/bluetooth/hci_uart_async/ |
| D | prj.conf | 23 # in case it has a interfering default. Those same boards set this
|
| /Zephyr-latest/tests/bsim/bluetooth/host/misc/disconnect/dut/ |
| D | prj.conf | 20 # Enable those as needed
|
| /Zephyr-latest/soc/silabs/common/ |
| D | soc_power_pmgr.c | 84 * for that they had to include sl_power_manager.h during build. Some of those
93 * definition here just to satisfy those blobs. It will also be used if we
|
| /Zephyr-latest/doc/build/snippets/ |
| D | index.rst | 7 those settings when you build any Zephyr application. This lets you save common
|
| /Zephyr-latest/tests/bsim/bluetooth/host/att/sequential/dut/ |
| D | prj.conf | 23 # Enable those as needed
|
12345678910>>...23
