Searched refs:changes (Results 51 – 75 of 191) sorted by relevance
12345678
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_mac.rst | 24 make changes and check the checkbox corresponding to your terminal emulator of
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | setting.rst | 15 Before making changes to Kconfig files, it's a good idea to also go through
22 When making Kconfig changes, it's important to understand the difference
197 configuration that gets modified when making changes in the :ref:`interactive
210 ensure you always have a locally named setting, even if the external setting name changes.
253 When making changes to the default configuration for a board, you might have to
346 When making changes to :file:`Kconfig.defconfig` files, always check the
|
| D | menuconfig.rst | 7 available Kconfig options and making temporary changes: ``menuconfig`` and
88 idea to check any changes to Kconfig files you make in *single-menu
126 save-and-quit dialog (if there are changes to save):
|
| /Zephyr-latest/samples/bluetooth/iso_broadcast_benchmark/ |
| D | README.rst | 90 The broadcaster will ask if any changes to the current settings are wanted.
91 If y/Y is chosen, then it will create a prompt to enter changes to the settings,
|
| /Zephyr-latest/samples/bluetooth/iso_connected_benchmark/ |
| D | README.rst | 86 The central will ask if any changes to the current settings are wanted.
87 If y/Y is chosen, then it will create a prompt to changes the settings,
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.6.rst | 26 A detailed list of changes since v1.5.0 by component follows:
231 * ``ZEP-925`` - API changes to message queues
232 * ``ZEP-926`` - API changes to memory pools
233 * ``ZEP-927`` - API changes to memory maps
234 * ``ZEP-928`` - API changes to event handling
264 * ``ZEP-1047`` - Adapt to new PM related boot flow changes in QMSI boot loader
277 * ``ZEP-1386`` - Revise power management document to reflect latest changes
|
| D | release-notes-3.7.rst | 16 It changes the way both SoCs and boards are named, defined and constructed in Zephyr.
43 An overview of the changes required or recommended when migrating your application from Zephyr
47 enhancements and changes since previous LTS release, Zephyr 2.7.0, include:
65 * Summary of breaking changes (refer to release notes and migration guides from previous release
79 The following sections provide detailed lists of changes by component.
378 * Made these changes in other SoC series:
442 * Made these board changes:
450 * Updated the Linkserver west runner to reflect changes to the CLI of LinkServer v1.5.xx
572 * Sample changes
581 * ADI AD559x changes
[all …]
|
| /Zephyr-latest/doc/contribute/documentation/ |
| D | generation.rst | 218 file in an error message, as these changes will not be saved.
248 When making and testing major changes to the documentation, we provide an option
284 it locally, and watch the documentation directory for changes. When changes are
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | comparator.rst | 13 Comparators can typically set a trigger which triggers on output changes. This trigger can
|
| /Zephyr-latest/include/zephyr/arch/posix/ |
| D | linker.ld | 92 * Note that the INSERT command actually changes the meaning of the -T command
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | heartbeat.rst | 40 The node publishes a new Heartbeat message every time a feature changes. The
|
| /Zephyr-latest/doc/services/pm/ |
| D | power_domain.rst | 10 powered by a common source to be notified of power source state changes in a
143 All devices under a domain will be notified when the domain changes
|
| /Zephyr-latest/doc/security/ |
| D | secure-coding.rst | 45 incorporate changes into the Zephyr codebase. This is followed by
49 Finally, the document covers how changes are to be made to this
123 - **Change management**: to guarantee a traceability of changes to the
188 project's code base, is comfortable making changes to it, and is
239 The Zephyr project shall use a code review system that all changes are
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/shell_mgmt/ |
| D | Kconfig | 33 changes to the CONFIG_SHELL_CMD_BUFF_SIZE may increase stack size
|
| /Zephyr-latest/drivers/ethernet/phy/ |
| D | Kconfig | 92 periodically executed to detect and report any changes in the
|
| /Zephyr-latest/samples/tfm_integration/tfm_secure_partition/ |
| D | README.rst | 30 both the secure and non-secure CMakeLists.txt file and make relevant changes, as well as the yaml
|
| /Zephyr-latest/cmake/ |
| D | target_toolchain_flags.cmake | 6 # after symlinks are resolved. This ensure that if the content changes, then
|
| /Zephyr-latest/samples/basic/rgb_led/ |
| D | README.rst | 18 range of color changes from the RGB LED, and the sample repeats forever.
|
| /Zephyr-latest/subsys/bluetooth/audio/ |
| D | Kconfig.csip | 52 This option enables support for clients to be notified on SIRK changes.
|
| /Zephyr-latest/cmake/modules/ |
| D | user_cache.cmake | 23 # then no changes to the variable will happen.
|
| /Zephyr-latest/subsys/bluetooth/services/ |
| D | Kconfig.dis | 94 When upward-compatible changes are made to the device, it is recommended
95 that the minor version number be incremented. If incompatible changes are
|
| /Zephyr-latest/doc/services/storage/nvs/ |
| D | nvs.rst | 114 changes the supported minimal write block size.
116 physical ATE size changes.
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_backporting.rst | 10 changes to Zephyr version 2.7 LTS
75 Even if some of the commits require changes, keep the commit messages of all the ported commits
|
| /Zephyr-latest/doc/develop/tools/ |
| D | clion.rst | 75 Click :guilabel:`Apply` to save the changes.
89 #. Click :guilabel:`Apply` to save the changes.
|
| /Zephyr-latest/doc/kernel/ |
| D | timeutil.rst | 124 * A time scale is *continuous* if the representation has no abrupt changes in
142 changes in Earth’s rotation. Thus the difference between TAI and UT varies
208 seconds and local time offset changes. This may be best provided by an
|
12345678
