Home
last modified time | relevance | path

Searched refs:copying (Results 1 – 25 of 40) sorted by relevance

12

/Zephyr-latest/boards/renesas/da1469x_dk_pro/
DKconfig.defconfig24 # the DMA is copying data into driver's frame buffer.
/Zephyr-latest/doc/services/
Dnotify.rst25 * copying the notification content from userspace will break use of
/Zephyr-latest/boards/shields/v2c_daplink/doc/
Dindex.rst41 manually by copying the resulting ``zephyr/zephyr.bin`` file to the USB mass
/Zephyr-latest/doc/hardware/peripherals/sensor/
Dindex.rst77 :c:struct:`sensor_trigger` rather than copying the contents. This is so
94 the provided buffer avoiding copying of any kind, with few exceptions.
/Zephyr-latest/drivers/ethernet/
DKconfig.xmc4xxx36 forwarded to the network stack without copying the data. The buffers
/Zephyr-latest/boards/shields/frdm_kw41z/doc/
Dindex.rst42 #. Program the binary to flash by copying it to the USB mass storage device.
/Zephyr-latest/boards/madmachine/mm_swiftio/doc/
Dindex.rst155 external flashes on this board so you must flash the device by copying files
/Zephyr-latest/doc/services/llext/
Dconfig.rst62 buffer in RAM and copying it is not necessary. The following option allows the
/Zephyr-latest/doc/kernel/memory_management/
Dslabs.rst141 to another, to avoid unnecessary copying of the data.
/Zephyr-latest/doc/kernel/data_structures/
Dmpsc_pbuf.rst14 on packet is freed. This approach reduces memory copying.
Dring_buffers.rst10 "streaming" copying of data, Zephyr provides a ``struct ring_buf``
134 Data can be retrieved from a ring buffer through copying
/Zephyr-latest/boards/nxp/twr_kv58f220m/doc/
Dindex.rst105 used for flashing the KV58 SoC by copying the compiled firmware to the USB Mass
/Zephyr-latest/boards/mediatek/
Dindex.rst63 Once you have the device set up, the process is as simple as copying
/Zephyr-latest/arch/xtensa/core/
DREADME_WINDOWS.rst34 to WINDOWBASE, at the same time copying the old (now hidden) stack
/Zephyr-latest/doc/services/storage/nvs/
Dnvs.rst68 sector is always kept empty to allow copying of existing data.
/Zephyr-latest/boards/phytec/phyboard_pollux/doc/
Dindex.rst243 or from U-boot by directly copying the firmware binary. Please check the
/Zephyr-latest/cmake/
Dllext-edk.cmake5 # build an llext extension. It does so by copying all headers accessible from
/Zephyr-latest/boards/nxp/imx8mm_evk/doc/
Dindex.rst220 Load and run Zephyr on M4 from A53 using u-boot by copying the compiled
/Zephyr-latest/doc/services/tracing/
Dindex.rst550 E.g. DMA, or zero-copying in shared memory.
574 E.g. Blocking read-call, ``fread()`` or SPI-read, zero-copying in shared
582 E.g. zero-copying in shared memory.
/Zephyr-latest/boards/nxp/mimxrt1180_evk/doc/
Dindex.rst269 The CM33 core is responsible for copying and starting the CM7.
/Zephyr-latest/doc/connectivity/networking/
Doverview.rst124 copy network data path. This means that the system tries to avoid copying
/Zephyr-latest/boards/toradex/verdin_imx8mm/doc/
Dindex.rst178 Load and run Zephyr on M4 from A53 using u-boot by copying the compiled
/Zephyr-latest/doc/kernel/services/data_passing/
Dmailboxes.rst425 the message without copying the data.
435 certain criteria, thereby eliminating unneeded data copying. The message
/Zephyr-latest/doc/
Dglossary.rst192 term storage rather than copying it into RAM, saving writable memory for
/Zephyr-latest/boards/nxp/imx8mp_evk/doc/
Dindex.rst201 Load and run Zephyr on M7 from A53 using u-boot by copying the compiled

12