Home
last modified time | relevance | path

Searched refs:shell (Results 1476 – 1489 of 1489) sorted by relevance

1...<<51525354555657585960

/Zephyr-latest/boards/espressif/esp32_ethernet_kit/doc/
Dindex.rst540 .. code-block:: shell
/Zephyr-latest/doc/build/dts/
Dhowtos.rst125 on user input like in a shell application. In this case you can get the
/Zephyr-latest/doc/develop/flash_debug/
Dprobes.rst453 shell>
/Zephyr-latest/drivers/wifi/nrf_wifi/
DKconfig.nrfwifi199 bool "Utility shell in nRF70 driver"
/Zephyr-latest/boards/openisa/rv32m1_vega/doc/
Dindex.rst516 The above only sets these variables for your current shell session.
/Zephyr-latest/doc/releases/
Drelease-notes-2.2.rst438 * Added I2C shell with scan command
516 * Introduced sensor shell module
/Zephyr-latest/doc/develop/west/
Dmanifest.rst1080 .. code-block:: shell
1672 to match against. This is a shell-style globbing pattern, currently
/Zephyr-latest/doc/contribute/
Dguidelines.rst409 * ``Bluetooth: Shell:`` for changes to the Bluetooth shell
/Zephyr-latest/doc/hardware/porting/
Dboard_porting.rst660 CDC ACM UART as the default backend for logging and shell.
/Zephyr-latest/
D.ruff-excludes.toml708 "./scripts/pylib/pytest-twister-harness/src/twister_harness/helpers/shell.py" = [
1576 "./scripts/pylib/pytest-twister-harness/src/twister_harness/helpers/shell.py",
/Zephyr-latest/doc/develop/application/
Dindex.rst310 For example, in a Unix shell or Windows ``cmd.exe`` prompt:
/Zephyr-latest/scripts/kconfig/
Dkconfiglib.py6834 command, shell=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE
/Zephyr-latest/subsys/bluetooth/mesh/
DKconfig1924 rsource "shell/Kconfig"
/Zephyr-latest/cmake/modules/
Dextensions.cmake2543 # can be specified by using shell-like quoting along with a 'SHELL:' prefix.

1...<<51525354555657585960