Searched refs:what (Results 201 – 225 of 245) sorted by relevance
12345678910
| /Zephyr-latest/subsys/debug/ |
| D | Kconfig | 252 fails, the policy for what to do is controlled by the implementation
|
| /Zephyr-latest/doc/build/dts/ |
| D | api-usage.rst | 350 driver implements support for. This ``compat`` value is what you would pass to
|
| D | intro-syntax-structure.rst | 68 array of what are called *cells*. A cell is just a 32-bit unsigned integer.
|
| D | howtos.rst | 181 :ref:`dt-bindings` are YAML files which declare what you can do with the nodes
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | setting.rst | 115 the symbol are satisfied. A warning is printed otherwise. To figure out what
|
| /Zephyr-latest/doc/develop/west/ |
| D | build-flash-debug.rst | 31 Its default behavior tries to "do what you mean":
408 - String, instructs west whether to try to guess what build folder to use
|
| D | manifest.rst | 161 specify what Git remote URLs to use when cloning and fetching the projects,
162 what revisions to track, and where the project should be stored on the local
2229 what decisions west made about your manifest, and why:
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | mcp.rst | 320 results are returned no matter what is searched for.
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/host/ |
| D | gap.rst | 26 Here is an example of what you can expect:
|
| /Zephyr-latest/doc/develop/tools/ |
| D | coccinelle.rst | 201 You can learn what these options are by using verbose option, you could
|
| /Zephyr-latest/kernel/ |
| D | Kconfig | 23 set to 'n'; disable only when you REALLY know what you are
755 size than what's specified by enabled subsystems. This can be useful
|
| /Zephyr-latest/doc/kernel/drivers/ |
| D | index.rst | 345 allow the user to specify at what time during the boot sequence the init
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | mailboxes.rst | 49 allowing both threads to know what has occurred.
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | memory_domain.rst | 204 - Care must be taken in determining what memory to expose in a partition.
|
| D | syscalls.rst | 237 The implementation function is what actually does the work for the API.
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-3.5.rst | 136 determining what we want to measure using solely the ADC API.
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 37 This iterable section can then be iterated over to find out what (if any) connectivity implementati…
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu.rst | 124 incoming firmware update, and what the effect of the update would be. The metadata format is
|
| /Zephyr-latest/doc/kernel/services/smp/ |
| D | smp.rst | 280 needs to reflect what is running locally, there are many threads
|
| /Zephyr-latest/doc/security/ |
| D | sensor-threat.rst | 415 As new exploits are discovered, what is considered secure can
|
| /Zephyr-latest/doc/ |
| D | zephyr.doxyfile.in | 1360 # footer and what special commands can be used inside the footer. See also
1909 # (what the <access key> is depends on the OS and browser, but it is typically
2075 # Note: Only use a user-defined header if you know what you are doing!
2087 # LATEX_HEADER for more information on how to generate a default footer and what
2090 # normally uses. Note: Only use a user-defined footer if you know what you are
2392 # understand what is going on. On the other hand, if this tag is set to NO, the
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 466 This section describes some of what you can do in your :file:`CMakeLists.txt`.
993 revisions, and what revisions are supported.
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 114 use sysbuild all the time, without worrying about what type of build you are
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | workqueue.rst | 488 to indicate that the result is intentionally ignored, and (2) documenting what
|
| /Zephyr-latest/ |
| D | CMakeLists.txt | 1429 # Essentially what we are doing here is extracting some information
1653 # application to know what the name of the final elf target is.
|
12345678910
