Searched refs:what (Results 151 – 175 of 245) sorted by relevance
12345678910
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig | 91 Says yes unless you are absolutely sure you know what you are
|
| /Zephyr-latest/doc/kernel/object_cores/ |
| D | index.rst | 53 The following table indicates both what objects have been integrated into the
|
| /Zephyr-latest/doc/build/dts/ |
| D | intro-input-output.rst | 125 what to do instead.
|
| /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/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/doc/connectivity/networking/api/ |
| D | net_mgmt.rst | 38 available procedure requests depend on what has been implemented in
|
| /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 | 114 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/subsys/bluetooth/ |
| D | Kconfig | 33 Select a custom, non-HCI based stack. If you're not sure what
|
| /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/dts/arm/raspberrypi/rpi_pico/ |
| D | rp2350.dtsi | 31 * define what kind of CPU cores they are.
|
| /Zephyr-latest/doc/contribute/ |
| D | contributor_expectations.rst | 288 what portion of the PR they reviewed. Examples of useful partial reviews
308 - Reviewers shall be *clear* and *concise* what changes they are requesting when the
|
| /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/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/boards/native/nrf_bsim/doc/ |
| D | nrf52_bsim.rst | 43 For more information on what is modelled to which level of detail,
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | index.rst | 457 If you are unsure what name west uses for your board, ``west boards``
506 If in doubt about what to do, check your board's page in :ref:`boards`.
|
| /Zephyr-latest/samples/subsys/mgmt/updatehub/ |
| D | README.rst | 252 loaded on the board with version 1.0.0. It is important check what file
335 Then inform what ``version`` this image is:
|
| /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.
|
| /Zephyr-latest/doc/develop/west/ |
| D | troubleshooting.rst | 29 The ``git fetch`` command example in the last line above is what needs to
|
| /Zephyr-latest/cmake/modules/ |
| D | kernel.cmake | 183 # string that tells what nic model Qemu should use.
|
12345678910
