Searched refs:what (Results 226 – 245 of 245) sorted by relevance
12345678910
| /Zephyr-latest/doc/kernel/services/ |
| D | interrupts.rst | 701 runtime what vector is associated with an IRQ line. :ref:`gen_idt.py` additionally
|
| /Zephyr-latest/doc/develop/west/ |
| D | release-notes.rst | 502 enabled and disabled to determine what projects are "active", and therefore
|
| /Zephyr-latest/drivers/wifi/nxp/ |
| D | Kconfig.nxp | 1185 Enabling this will help you to monitor what
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | Kconfig | 339 beyond what is described in the specification. Enabling this option
|
| /Zephyr-latest/doc/contribute/documentation/ |
| D | guidelines.rst | 908 A whitespace-separated list of what to do with the app (any of ``build``, ``flash``,
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | board_porting.rst | 736 To see what a ``west flash`` or ``west debug`` command is doing exactly, run it
|
| /Zephyr-latest/doc/services/zbus/ |
| D | index.rst | 133 enable the developer to be as free as possible to create what they need. For example, messages can
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/ |
| D | hci.txt | 1092 The Error_Data_Type provides an information about what is the Error_Data size
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.13.rst | 624 * :github:`7106` - tests: obj_tracing: Test fails on ESP32, semaphore count is more than what is cr…
|
| D | release-notes-2.1.rst | 634 * :github:`20032` - Make it clear in HTML docs what monospaced text is a link
|
| D | release-notes-3.4.rst | 206 has been replaced with an enum to indicate what function is used, see
|
| D | release-notes-3.6.rst | 118 are made to what listener will be granted the object, as only the first claim is served.
|
| D | release-notes-3.0.rst | 89 devicetree binding's ``fem`` property for information on what to do instead
|
| D | release-notes-2.6.rst | 1364 * :github:`34474` - MPS2-AN385 SRAM does not match what the documentation page says
|
| D | release-notes-3.2.rst | 1627 * Refactored and optimized the code, mainly in what affects the progressive erase implementation.
|
| D | release-notes-1.14.rst | 2071 * :github:`10318` - It is not documented what YAML bindings do
|
| /Zephyr-latest/doc/contribute/coding_guidelines/ |
| D | index.rst | 1289 non-measurable component to what "commonly used" means, the ultimate goal is
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | shell.rst | 1260 from the given DFU image slot to the Target node's DFU image at the given index, and what
|
| /Zephyr-latest/cmake/modules/ |
| D | extensions.cmake | 434 # Determines what the current directory's lib name would be according to the
|
| /Zephyr-latest/samples/modules/tflite-micro/hello_world/train/ |
| D | train_hello_world_model.ipynb | 1639 …"To get more insight into what is happening, let's check its predictions against the test dataset …
|
12345678910
