Searched refs:changes (Results 101 – 125 of 200) sorted by relevance
12345678
| /Zephyr-latest/doc/build/version/ |
| D | index.rst | 58 manually re-ran for changes to this file.
|
| /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
|
| D | built-in.rst | 10 on the entire workspace. For example, ``west diff`` shows local changes in
161 ignore incoming changes for the moment.
|
| /Zephyr-latest/cmake/modules/ |
| D | kconfig.cmake | 13 # Re-configure (Re-execute all CMakeLists.txt code) when autoconf.h changes
379 # Force CMAKE configure when the Kconfig sources or configuration files changes.
|
| /Zephyr-latest/doc/releases/ |
| 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 …]
|
| D | migration-guide-3.7.rst | 8 This document describes the changes required when migrating your application from Zephyr v3.6.0 to
11 Any other changes (not directly related to migrating applications) can be found in
856 nothing changes from the user point of view. But, if there is more than
865 There are no API changes, but the type of a VLAN network interface is changed from ``ETHERNET``
866 to ``VIRTUAL``. This could require changes to the code that sets the VLAN tags to a network
950 changes to Kconfig files (``prj.conf``, etc), as outlined in the release notes. A more automated
|
| D | release-notes-3.6.rst | 25 An overview of the changes required or recommended when migrating your application from Zephyr
28 The following sections provide detailed lists of changes by component.
155 * Made these changes in other SoC series:
194 * Made these changes for ARM boards:
204 * Made these changes for RISC-V boards:
208 * Made these changes for native/POSIX boards:
398 * Fixed ksz8081 driver. Logging changes, RMII clock fixes, GPIO pin fixes.
1292 Additionally, the following changes in Zephyr were done:
|
| D | release-notes-4.0.rst | 58 An overview of the changes required or recommended when migrating your application from Zephyr
61 The following sections provide detailed lists of changes by component.
244 * Made these changes in other SoC series:
339 * Made these board changes:
429 documentation when changes to the input ``.rst`` files are detected on the filesystem.
578 * PHY driver changes
601 state changes and SPI transfers between other operations, specifically when burst type
1297 * No significant changes in this release
1316 * LittleFS: The module has been updated with changes committed upstream
|
| D | release-notes-2.5.rst | 20 The following sections provide detailed lists of changes by component.
151 Stable API changes in this release
290 * Made these changes in other SoC series:
338 * Made these global changes in STM32 boards and SoC series:
351 * Made these changes in other boards:
643 * Send Registration Update on lifetime changes.
663 * Added support to update unique hostname on link address changes.
794 * Property access macro changes:
863 * New power state changes notification API :c:struct:`pm_notifier`
999 * :github:`31973` - Stm32 uart async driver changes offset after callback
[all …]
|
| D | release-notes-1.7.rst | 25 The following sections provide a detailed list of changes, by component, since
73 Because of this there is lot of changes in the code base. The native IP stack
399 * ``ZEP-1651`` - i2c_dw malfunctioning due to various changes.
|
| /Zephyr-latest/boards/cdns/xt-sim/doc/ |
| D | index.rst | 153 7. Hit ``Exit`` and confirm saving the changes.
|
| /Zephyr-latest/cmake/linker/armlink/ |
| D | scatter_script.cmake | 424 file(APPEND ${STEERING_C} " * AUTO-GENERATED - All changes will be lost\n")
442 file(APPEND ${STEERING_FILE} "; AUTO-GENERATED - All changes will be lost\n")
|
| /Zephyr-latest/doc/connectivity/usb/device_next/ |
| D | usb_device.rst | 150 :c:func:`usbd_init` does only what is necessary to detect VBUS changes. There
179 messages are mostly about the common device state changes, and a few specific
|
| /Zephyr-latest/doc/hardware/peripherals/can/ |
| D | controller.rst | 101 the node changes to error-passive state.
103 If the transmit-error counter increases further to 255, the node changes to the
|
| /Zephyr-latest/doc/services/portability/posix/overview/ |
| D | index.rst | 25 POSIX conformant can be ported to Zephyr kernel based applications with no changes.
|
| /Zephyr-latest/ |
| D | CODE_OF_CONDUCT.md | 125 The only changes made by The Zephyr Project to the original document were to
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | images.rst | 217 As can be seen, no additional CMake changes are needed to add an alternative image as the base
336 ``ExternalZephyrProject_Add()`` require changes to sysbuild code in Zephyr. This should only be
|
| /Zephyr-latest/boards/nxp/rd_rw612_bga/doc/ |
| D | index.rst | 126 connected via jumper wires. Connections and required board changes are
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_mgmt.rst | 18 a network interface IP address changes.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | core.rst | 76 device configuration persistently. When the stack configuration changes and
|
| /Zephyr-latest/doc/develop/ |
| D | env_vars.rst | 75 your changes by clicking the Save button at top left before exiting. Settings
|
| /Zephyr-latest/doc/build/cmake/ |
| D | index.rst | 18 most code changes. However, after certain changes, the configuration step must
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 61 application-specific changes which should be applied to the base devicetree
274 needed. Make any other changes you need to other files.
295 From now on, you can collaborate on the shared software by pushing changes to
908 Application development is usually fastest when changes are continually tested.
911 rebuild and test after any major changes to the application's source files,
917 potentially affected by the changes. Consequently, rebuilding an application
|
| /Zephyr-latest/doc/security/ |
| D | reporting.rst | 154 to determine if they need to backport these changes to any internal
|
12345678
