/Zephyr-latest/tests/drivers/gpio/gpio_basic_api/boards/ |
D | rpi_pico2_rp2350a_m33.overlay | 7 /* Pico 2 is compatible with the Pico 1, so reuse. */
|
D | pico_plus2_rp2350b_m33.overlay | 7 /* Pico Plus2 is pin-compatible with the RPi-Pico, so reuse. */
|
/Zephyr-latest/samples/sensor/die_temp_polling/boards/ |
D | rpi_pico2_rp2350a_m33.overlay | 7 /* Pico 2 is compatible with the Pico 1, so reuse. */
|
/Zephyr-latest/cmake/compiler/host-gcc/ |
D | compiler_flags.cmake | 2 # Significant overlap with freestanding gcc compiler so reuse it
|
/Zephyr-latest/tests/drivers/gpio/gpio_api_1pin/boards/ |
D | pico_plus2_rp2350b_m33.overlay | 7 /* Pico Plus2 is pin-compatible with the RPi-Pico2, so reuse. */
|
/Zephyr-latest/tests/drivers/dma/chan_blen_transfer/socs/ |
D | rp2350a_m33.overlay | 7 /* RP2350A is compatible with the RP2040, so reuse. */
|
/Zephyr-latest/tests/drivers/dma/loop_transfer/boards/ |
D | rpi_pico2_rp2350a_m33.overlay | 7 /* Pico 2 is compatible with the Pico 1, so reuse. */
|
/Zephyr-latest/samples/boards/raspberrypi/rpi_pico/uart_pio/boards/ |
D | rpi_pico2_rp2350a_m33.overlay | 7 /* Pico 2 is compatible with the Pico 1, so reuse. */
|
/Zephyr-latest/samples/drivers/adc/adc_dt/boards/ |
D | rpi_pico2_rp2350a_m33.overlay | 7 /* Pico 2 is compatible with the Pico 1, so reuse. */
|
/Zephyr-latest/samples/drivers/led/pwm/boards/ |
D | rpi_pico2_rp2350a_m33.overlay | 7 /* Pico 2 is compatible with the Pico 1, so reuse. */
|
/Zephyr-latest/tests/drivers/adc/adc_api/boards/ |
D | rpi_pico2_rp2350a_m33.overlay | 7 /* Pico 2 is compatible with the Pico 1, so reuse. */
|
/Zephyr-latest/doc/develop/toolchains/ |
D | host.rst | 7 a Linux host, you may be able to reuse the native development tools provided
|
/Zephyr-latest/tests/net/socket/tls_ext/ |
D | CMakeLists.txt | 28 # we reuse the same certificate / private key for client
|
/Zephyr-latest/drivers/usb/device/ |
D | usb_dc_native_posix_adapt.c | 266 int reuse = 1; in usbip_start() local 287 (const char *)&reuse, sizeof(reuse)) < 0) { in usbip_start()
|
/Zephyr-latest/boards/nxp/mimxrt1062_fmurt6/ |
D | CMakeLists.txt | 11 # the SDK, but we can reuse the block for the RT1050 as FMURT6 also uses
|
/Zephyr-latest/tests/net/lib/http_server/tls/ |
D | CMakeLists.txt | 31 # we reuse the same certificate / private key for client
|
/Zephyr-latest/samples/subsys/lorawan/class_a/ |
D | README.rst | 40 …NFIG_LORAWAN_NVM_SETTINGS` in the Kconfig. This allows proper storage and reuse of configuration s…
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | video.rst | 34 release or reuse.
|
/Zephyr-latest/doc/develop/manifest/external/ |
D | cannectivity.rst | 24 The CANnectivity firmware repository is a Zephyr :ref:`module <modules>` which allows for reuse of
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | websocket.rst | 66 the lifecycle(close/reuse) of tcp socket after websocket_disconnect.
|
/Zephyr-latest/boards/nxp/mimxrt1060_evk/ |
D | CMakeLists.txt | 23 # the SDK, but we can reuse the block for the RT1050 as both boards use
|
/Zephyr-latest/boards/native/nrf_bsim/ |
D | Kconfig | 99 # Let's reuse the RTC sync options so applications which use it can be reused as is
|
/Zephyr-latest/subsys/usb/host/ |
D | usbip.c | 645 int reuse = 1; in usbip_thread_handler() local 656 (const char *)&reuse, sizeof(reuse)) < 0) { in usbip_thread_handler()
|
/Zephyr-latest/boards/adi/max78000evkit/doc/ |
D | index.rst | 263 | | | | All Open | | | Disables USB-UART0 bridge, allows reuse of… 270 | | | | All Open | | | Disables USB-UART1 bridge, allows reuse of…
|
/Zephyr-latest/doc/contribute/ |
D | index.rst | 92 available in other open source projects, and it is recommended and encouraged to reuse such code.
|