Searched refs:what (Results 151 – 175 of 252) sorted by relevance
1234567891011
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-syntax.rst | 50 # SPI memory chip, use 'on-bus:' to say what type of bus, like this.
513 If the node is a bus controller, use ``bus:`` in the binding to say what type
544 what type of bus.
567 what bus it appears on. For example, consider a sensor device with compatible
|
| D | intro-input-output.rst | 125 what to do instead.
|
| /Zephyr-latest/doc/project/ |
| D | working_groups.rst | 72 unable to reach consensus on what advice to offer, the working group Chair
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | eth_bridge_native_sim_setup.rst | 27 The ``-i`` option tells what is the first host interface name. The ``-t`` tells how
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_if.rst | 46 See Kconfig file :zephyr_file:`subsys/net/ip/Kconfig` what options are available for
|
| D | net_mgmt.rst | 38 available procedure requests depend on what has been implemented in
|
| /Zephyr-latest/boards/cdns/xt-sim/doc/ |
| D | index.rst | 46 #aptitude install gcc-multilib # Or what ever package manager (apt, apt-get, ...)
|
| /Zephyr-latest/doc/develop/languages/c/ |
| D | picolibc.rst | 32 available to adjust the feature set in the library, balancing what the
|
| /Zephyr-latest/doc/connectivity/usb/device_next/ |
| D | usb_device.rst | 150 :c:func:`usbd_init` does only what is necessary to detect VBUS changes. There
245 the implementation of these functions checks in what context they are called
|
| /Zephyr-latest/ |
| D | CODE_OF_CONDUCT.md | 25 * Focusing on what is best not just for us as individuals, but for the overall
|
| /Zephyr-latest/doc/kernel/object_cores/ |
| D | index.rst | 53 The following table indicates both what objects have been integrated into the
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig | 91 Says yes unless you are absolutely sure you know what you are
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu_srv.rst | 49 Distributor, and should indicate what effect the firmware update will have on the mesh state of the
|
| /Zephyr-latest/samples/net/capture/ |
| D | README.rst | 15 same connection as what we are capturing packets or it can be a separate
|
| /Zephyr-latest/modules/hal_nordic/ |
| D | Kconfig | 122 you know what you are doing.
|
| /Zephyr-latest/doc/services/tfm/ |
| D | overview.rst | 6 `IoT Security Framework <https://www.psacertified.org/what-is-psa-certified/>`__.
32 has certain implications about what the Zephyr application image can and can
|
| /Zephyr-latest/boards/native/doc/ |
| D | arch_soc.rst | 81 The underlying assumptions behind this port set some limitations on what
317 but it is not a requirement for other POSIX arch based boards to follow what is described here.
338 The result of this build is a pre-linked elf library, which contains what we can call the
|
| /Zephyr-latest/doc/services/storage/nvs/ |
| D | nvs.rst | 108 From this formula it is also clear what to do in case the expected life is too
|
| /Zephyr-latest/doc/services/ipc/ipc_service/backends/ |
| D | ipc_service_icbmsg.rst | 181 It is up to the implementation to decide what to do if no blocks are available.
206 The first byte tells what kind of message it is.
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | tips.rst | 405 To understand what's going on, remember that ``STACK_SIZE`` has a prompt,
419 The right fix depends on what the intention is. Here's some different scenarios
649 * Is it easy to guess what the symbols do from their prompts?
785 be what was intended compared to other symbol types as well.
|
| D | menuconfig.rst | 91 ``config`` and symbols defined with ``menuconfig``, showing you what
|
| /Zephyr-latest/dts/arm/raspberrypi/rpi_pico/ |
| D | rp2350.dtsi | 31 * define what kind of CPU cores they are.
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/os_mgmt/ |
| D | Kconfig | 71 Select what will serve as thread name in "taskstat" response.
|
| /Zephyr-latest/drivers/modem/ |
| D | Kconfig.hl7800 | 298 Do not mess with it unless you know what you are doing.
|
| /Zephyr-latest/subsys/shell/backends/ |
| D | Kconfig.backends | 506 It really depends on what type of output is expected.
637 It really depends on what type of output is expected.
|
1234567891011
