Searched refs:were (Results 26 – 50 of 136) sorted by relevance
123456
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | ieee802154.rst | 26 were accepted into the standard, namely IEEE 802.15.4g (SUN FSK) and IEEE
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | nothread.rst | 85 capabilities that were not originally implemented to work with threads
|
| /Zephyr-latest/cmake/ |
| D | package_helper.cmake | 22 # For example, if you were invoking CMake for 'hello_world' sample as:
|
| /Zephyr-latest/cmake/sca/codechecker/ |
| D | sca.cmake | 110 # issues were detected. Suppress the exit status by default, but permit opting
|
| /Zephyr-latest/doc/develop/west/ |
| D | sign.rst | 29 build logs to find which exact options were used. Copying these options from the
|
| D | release-notes.rst | 154 abbreviations were causing problems in practice when commands were updated to
209 - West commands that were run with a bad local configuration file dumped stack
357 which selected the default branch name were leaving the manifest repository
366 worked correctly for annotated tags; only lightweight tags were unnecessarily
449 lists from any imported manifests were ignored.
808 - Incompatible API changes were made to west's APIs. Further changes are
818 ``west.manifest.Manifest`` factory methods and constructor were also
|
| D | built-in.rst | 6 This page describes west's built-in commands, some of which were introduced in
138 leaving behind any branches which were already checked out. This is
183 value were appended to the ``manifest.group-filter``
|
| /Zephyr-latest/boards/enjoydigital/litex_vexriscv/doc/ |
| D | index.rst | 56 All drivers were tested using this platform.
159 If you were generating bitstream with the official LiteX SoC builder you need to pass an additional…
|
| /Zephyr-latest/cmake/modules/ |
| D | FindHostTools.cmake | 43 # True if all required host tools were found.
|
| D | FindTargetTools.cmake | 22 # True if all required host tools were found.
|
| D | snippets.cmake | 121 # If snippets were requested, print messages for each one.
|
| /Zephyr-latest/doc/security/ |
| D | reporting.rst | 127 allocate additional CVE numbers, or to retire numbers that were
133 Each Zephyr release shall contain a report of CVEs that were fixed in
|
| /Zephyr-latest/subsys/logging/ |
| D | Kconfig.misc | 48 (seen on arm_cortex_m and x86) were using unrealistic amount of stack
|
| /Zephyr-latest/subsys/mgmt/updatehub/ |
| D | Kconfig | 103 Configure the max size of a data payload were value:
|
| /Zephyr-latest/doc/services/resource_management/ |
| D | index.rst | 57 responsible for recording whether their requests were accepted, and for
|
| /Zephyr-latest/boards/adafruit/itsybitsy/doc/ |
| D | index.rst | 94 Some versions of this board were shipped with a buggy bootloader.
|
| /Zephyr-latest/doc/project/ |
| D | tsc.rst | 124 - Existing TSC members who were elected before May 2024 shall be re-confirmed
125 after completing the 2 year term since they were first elected.
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-3.5.rst | 245 The two new flags :c:macro:`ISOTP_MSG_FDF` and :c:macro:`ISOTP_MSG_BRS` were added for CAN FD
265 :kconfig:option:`CONFIG_PM` because empty weak stubs were provided, however,
306 * Ethernet PHY devicetree bindings were updated to use the standard ``reg``
310 corresponding driver were updated to consistently use the node name
|
| D | release-notes-4.2.rst | 60 * The scheduler Kconfig options CONFIG_SCHED_DUMB and CONFIG_WAITQ_DUMB were
|
| /Zephyr-latest/doc/services/storage/flash_map/ |
| D | flash_map.rst | 58 both MCUboot and a storage partition. Some details were left out for clarity.
|
| /Zephyr-latest/share/zephyr-package/cmake/ |
| D | ZephyrConfig.cmake | 154 # Ending here means there were no candidates in workspace of the app.
|
| /Zephyr-latest/scripts/coccinelle/ |
| D | int_ms_to_timeout.cocci | 7 // integer milliseconds, when they were intended to be timeout values
|
| /Zephyr-latest/doc/services/llext/ |
| D | load.rst | 72 pointers to symbols in the extension that were obtained will be invalid.
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | rtc.rst | 41 The disadvantages of this approach were that hardware counters could
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister_statuses.rst | 211 Whole suite was not run, but only built. It requires than all Cases within were not run.
|
123456
