Home
last modified time | relevance | path

Searched refs:needed (Results 176 – 200 of 450) sorted by relevance

12345678910>>...18

/Zephyr-latest/samples/net/sockets/txtime/
DKconfig12 a multicast address if needed. If port is not specified,
/Zephyr-latest/modules/hal_rpi_pico/
DCMakeLists.txt41 INSTALL_COMMAND "" # No installation needed
/Zephyr-latest/samples/bluetooth/direction_finding_connectionless_rx/
DREADME.rst30 changing ``nrf52833dk/nrf52833`` as needed for your board:
/Zephyr-latest/arch/arm/
DKconfig118 If needed, this hook can be used to prevent the CPU from actually
126 If needed, this hook can prepare data to upcoming call to
/Zephyr-latest/doc/hardware/peripherals/
Dmspi.rst56 static, boot time parameters. However, if needed, one can use :c:func:`mspi_config`
87 #. Register any callback with :c:func:`mspi_register_callback` if needed.
/Zephyr-latest/arch/arm/core/
DKconfig153 This is needed to conform to AAPCS, the procedure call standard for
166 needed, enable this option and attach it via z_arm_nmi_set_handler().
273 This is needed when switching between threads that differ in either
/Zephyr-latest/doc/hardware/porting/
Darch.rst6 An architecture port is needed to enable Zephyr to run on an :abbr:`ISA
48 likely be needed in the build system and when linking the image (required).
65 initialization sequence. Most of the time, very few steps are needed, while
311 :kconfig:option:`CONFIG_ARCH_HAS_THREAD_ABORT` as needed for the architecture (e.g. see
324 needed for thread local variables (excluding any extra data required by
344 check test suite, a system clock is needed as well. Since these two are usually
472 Some architecture-specific definitions are needed in :zephyr_file:`include/zephyr/toolchain/gcc.h`.
647 possible. They tend to be needed for two situations:
702 | Guard carve-out (if needed) |
709 The guard region, and any carve-out (if needed) would be configured as a
[all …]
/Zephyr-latest/drivers/serial/
DKconfig.ns16550102 interrupt controller may not see this new event. So if needed,
/Zephyr-latest/boards/01space/esp32c3_042_oled/doc/
Dindex.rst90 :ref:`sysbuild` makes it possible to build and flash all necessary images needed to
/Zephyr-latest/cmake/sca/eclair/
Dsca.cmake11 # Get eclair specific option file variables, also needed if invoked with sysbuild
/Zephyr-latest/doc/kernel/services/
Dindex.rst13 features needed by your application, making it ideal for systems with limited
/Zephyr-latest/samples/net/sockets/http_get/
DREADME.rst41 case no NAT/routing setup is needed).
/Zephyr-latest/modules/lvgl/
DKconfig.memory100 is needed to perform the conversion.
/Zephyr-latest/samples/bluetooth/direction_finding_connectionless_tx/
DREADME.rst30 ``nrf52833dk/nrf52833`` as needed for your board:
/Zephyr-latest/doc/connectivity/networking/
Dnet-stack-architecture.rst101 can check if the packet is proper and modify it if needed, e.g. strip L2
115 7. The application will then receive the data and can process it as needed.
/Zephyr-latest/doc/services/mem_mgmt/
Dindex.rst28 actually created. When it is needed to create an actual section out of the
192 MMU (if needed) and that an actual heap can be created out of it, for
/Zephyr-latest/subsys/net/lib/http/
DKconfig179 will be delayed by this value (miliseconds). The delay is needed to
204 needed by websocket console are set.
/Zephyr-latest/doc/kernel/data_structures/
Drbtree.rst15 before first use. No specific initialization API is needed or
61 buffer instead where needed to avoid the dynamic allocation). As with
/Zephyr-latest/cmake/modules/
Dunittest.cmake36 # Already a proper list, no conversion needed.
/Zephyr-latest/doc/build/dts/
Ddt-vs-kconfig.rst17 needed by the application, etc.
/Zephyr-latest/drivers/clock_control/
DKconfig.stm3266 needed to complete it. Since fLSI >= 24kHz, increasing the measurement window
/Zephyr-latest/samples/boards/nordic/coresight_stm/
DREADME.rst32 Host tool is needed to decode the logs.
/Zephyr-latest/arch/xtensa/core/
Dmpu.c505 uint8_t needed = (exact_s ? 0 : 1) + (exact_e ? 0 : 1); in mpu_map_region_add() local
508 if (first_enabled_idx < needed) { in mpu_map_region_add()
/Zephyr-latest/doc/safety/
Dsafety_requirements.rst62 #. Establish links between the requirements with the new attributed UIDs if needed
/Zephyr-latest/doc/services/retention/
Dblinfo.rst84 The following include is needed to use the bootloader information subsystem:

12345678910>>...18