Searched refs:changes (Results 76 – 100 of 191) sorted by relevance
12345678
| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | condvar.rst | 30 Some other thread, when it changes said state, can then wake one (or more)
|
| /Zephyr-latest/doc/ |
| D | index.rst | 86 For information about the changes and additions for past releases, please
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-3.5.rst | 8 This document describes the changes required or recommended when migrating your
11 Any other changes (not directly related to migrating applications) can be found in
14 Required changes
44 changes some internal operations within the kernel that improve
408 will be removed in future releases. Note that these changes do not apply to
|
| D | release-notes-3.4.rst | 36 The following sections provide detailed lists of changes by component.
190 :c:struct:`smp_transport_api_t`. Because of these changes, the legacy
198 implemented for the STM32 DAC driver. Implicitly for this driver this changes
253 Stable API changes in this release
511 * Made these changes in other SoC series:
563 * Made these changes for ARC boards:
571 * Made these changes for ARM boards:
586 * Made these changes for ARM64 boards:
590 * Made these changes to POSIX boards:
601 * Made these changes for RISC-V boards:
[all …]
|
| D | release-notes-1.5.rst | 9 Additional changes include support for new drivers, sensors, and boards.
20 A detailed list of changes since v1.4.0 by component follows:
226 * ``ZEP-525`` - srctree changes are breaking applications
|
| D | release-notes-1.11.rst | 25 The following sections provide detailed lists of changes by component.
42 * User space and system call related changes:
209 * :github:`2107` - handle configuration changes with more code coverage
278 * :github:`4025` - Upgrade to TinyCrypt 0.2.7 has significant API changes
317 * :github:`5010` - changes to included linker scripts are not picked up by the build system
440 * :github:`5938` - Incorrectly reported coverage changes
|
| D | release-notes-3.5.rst | 26 An overview of the changes required or recommended when migrating your application from Zephyr
29 The following sections provide detailed lists of changes by component.
218 * Mesh Protocol v1.1 changes
299 * Made these changes in other SoC series:
351 * Made these changes for ARC boards:
356 * Made these changes for ARM boards:
364 * Made these changes for ARM64 boards:
366 * Made these changes for RISC-V boards:
368 * Made these changes for X86 boards:
370 * Made these changes for Xtensa boards:
[all …]
|
| /Zephyr-latest/doc/build/dts/ |
| D | design.rst | 7 changes are expected. The following are the general design goals, along with
|
| /Zephyr-latest/tests/drivers/watchdog/wdt_error_cases/ |
| D | README.txt | 37 support wdt_disable() may require changes to the code.
|
| /Zephyr-latest/doc/contribute/ |
| D | index.rst | 41 Learn when and how to submit RFCs (Request for Comments) for new features and changes to the
|
| /Zephyr-latest/cmake/modules/ |
| D | configuration_files.cmake | 21 # loaded, then no changes to the variable will happen.
|
| /Zephyr-latest/doc/safety/ |
| D | safety_requirements.rst | 87 * Avoid creating large commits that contain both trivial and non-trivial changes.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/ |
| D | gatt.rst | 58 Attribute value changes can be notified using :c:func:`bt_gatt_notify` API,
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | tips.rst | 373 structure of the Kconfig files harder to understand, and also make changes more
465 It is a good idea to try out changes in the ``menuconfig`` or ``guiconfig``
467 especially true when making moderately complex changes like these.
630 Checking changes in menuconfig/guiconfig
633 When adding new symbols or making other changes to Kconfig files, it is a good
667 Checking changes with :file:`scripts/kconfig/lint.py`
670 After you make Kconfig changes, you can use the
|
| /Zephyr-latest/tests/kernel/context/ |
| D | README.txt | 45 count changes.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu.rst | 127 information can be image signatures, changes to the node's Composition Data and the format of the
208 This effect is chosen when the composition data changes and the device doesn't support the remote
211 This effect is chosen when the composition data changes and the device supports the remote
215 This effect is chosen if the composition data in the new firmware changes, the device doesn't
|
| /Zephyr-latest/doc/develop/ |
| D | beyond-GSG.rst | 86 by default. Proceed to next step without making any changes.
129 changes, caused, for example, when you pull the :file:`zephyr`
137 changes via ``git``. Afterwards, run ``west update`` as mentioned in
|
| /Zephyr-latest/samples/ |
| D | sample_definition_and_criteria.rst | 81 sample when changes are submitted to the Zephyr tree via a pull-request.
|
| /Zephyr-latest/samples/modules/chre/ |
| D | README.rst | 23 #. *Sensor* - a framework allowing nanoapps to request changes to sensors configuration get
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/ |
| D | README.rst | 118 avoid regressions on changes in the underlying layers.
|
| /Zephyr-latest/doc/security/ |
| D | security-overview.rst | 77 changes are identified, they will be added to this document through the
83 2. The Zephyr Security Subcommittee will review these changes and provide feedback
84 or acceptance of the changes.
86 3. Once accepted, these changes will become part of the document.
345 - **Change management:** to guarantee a traceability of changes to the
569 and before major changes of the module or system architecture.
|
| /Zephyr-latest/doc/develop/west/ |
| D | why.rst | 31 repositories without having to make changes to the zephyr repository
|
| D | without-west.rst | 45 As you pull changes in the zephyr repository, you will also need to
|
| /Zephyr-latest/doc/build/version/ |
| D | index.rst | 58 manually re-ran for changes to this file.
|
| /Zephyr-latest/boards/arm/fvp_baser_aemv8r/doc/ |
| D | debug-with-arm-ds.rst | 133 After all these changes are made, click ``Apply``, then click ``Debug``. DS will
|
12345678
