Searched refs:were (Results 76 – 100 of 136) sorted by relevance
123456
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-4.0.rst | 71 * The following Kconfig symbols were renamed (:github:`76408`):
573 * The following new symbols were added to allow specifying both the signature
|
| D | release-notes-2.2.rst | 16 The following security vulnerabilities (CVE) were addressed in this release:
29 These GitHub issues were addressed since the previous 2.2.0 tagged
67 The following security vulnerabilities (CVEs) were addressed in this release:
133 were reworked to honor pin active level. Any external users of these
718 These GitHub issues were addressed since the previous 2.1.0 tagged
|
| D | release-notes-1.12.rst | 32 unallocated memory. Proper overflow checks were added to fix this
265 * Discovered some API docs were missing, and fixed
284 These GitHub issues were closed since the previous 1.11.0 tagged release:
640 * :github:`7437` - Zephyr's mailing list archives were hard to find
|
| D | release-notes-1.11.rst | 184 These GitHub issues were addressed since the previous 1.10.0 tagged
334 * :github:`5270` - Not all IEEE802154_MCR20A_RAW references were removed
|
| D | release-notes-3.5.rst | 586 were removed as they were not aligned with the standard and some already
588 range (notably SUN FSK and HRP UWB drivers). The capabilities were replaced
861 were more precisely specified and all in-tree call sites updated accordingly.
2067 * Fixed an issue with MCUmgr fs_mgmt group whereby some status codes were not
|
| D | release-notes-1.10.rst | 182 if any new/unexpected warnings or errors were detected.
200 These GitHub issues were addressed since the previous 1.9.0 tagged
|
| /Zephyr-latest/doc/develop/test/ |
| D | ztest.rst | 125 Some tests were made to be broken. In cases where the test is expected to fail or skip due to the
309 level, i.e. if test cases have passed or failed or if they were blocked or skipped.
|
| /Zephyr-latest/subsys/bluetooth/ |
| D | Kconfig | 354 parameters for creating a CIG or a BIG. These test parameters were
|
| /Zephyr-latest/cmake/modules/ |
| D | kconfig.cmake | 376 # Read out the list of 'Kconfig' sources that were used by the engine.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | sockets.rst | 50 meaning that only 100 bytes were read (short read), and the application
|
| /Zephyr-latest/doc/develop/west/ |
| D | manifest.rst | 428 were introduced in some version of west. Attempts to load the manifest with
452 about the manifest file features that were introduced in that version.
463 that are not otherwise mentioned in this table were introduced in
475 that were introduced in west v0.9.0. You should ignore version "0.9" if
519 assumes that it should try to load it using the features that were available in
1421 contents of imported manifests as they were committed to the latest
|
| /Zephyr-latest/doc/services/storage/settings/ |
| D | index.rst | 148 signalling the application that the settings were successfully
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_callbacks.rst | 33 were registered.
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_linux.rst | 256 If this fails, make sure Zephyr's dependencies were installed as described
|
| /Zephyr-latest/boards/arm/v2m_musca_s1/doc/ |
| D | index.rst | 355 Reset the board, and if you were building the hello_world application you should
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | kernelobjects.rst | 205 * Kernel objects that were declared with static initialization macros
|
| /Zephyr-latest/doc/develop/languages/cpp/ |
| D | index.rst | 218 from its very beginning. They were not officially added to C until C11.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | access.rst | 251 the order they were passed to the access layer. This is because some messages can be delayed
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | setting.rst | 351 interfaces. If all board configuration were done via :file:`<BOARD>_defconfig`,
|
| /Zephyr-latest/doc/build/cmake/ |
| D | index.rst | 252 relationships between devices that were recorded from devicetree data,
|
| /Zephyr-latest/doc/services/llext/ |
| D | debug.rst | 10 symbols were available, it would be impossible for the debugger to know the
|
| /Zephyr-latest/arch/riscv/ |
| D | Kconfig | 192 be implemented in assembly. If they were C functions, they
|
| /Zephyr-latest/doc/build/ |
| D | zephyr_cmake_package.rst | 243 The following configuration files were considered but not accepted:
|
| /Zephyr-latest/doc/services/pm/ |
| D | device.rst | 86 from a sleep state, devices are resumed in the opposite order that they were
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/host/ |
| D | gap.rst | 98 If you were scanning just before, you can connect to the last scanned device by
|
123456
