Home
last modified time | relevance | path

Searched refs:changes (Results 101 – 125 of 191) sorted by relevance

12345678

/Zephyr-latest/boards/cdns/xt-sim/doc/
Dindex.rst153 7. Hit ``Exit`` and confirm saving the changes.
/Zephyr-latest/doc/releases/
Dmigration-guide-4.1.rst8 This document describes the changes required when migrating your application from Zephyr v4.0.0 to
11 Any other changes (not directly related to migrating applications) can be found in
Dmigration-guide-3.7.rst8 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
Drelease-notes-3.6.rst25 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:
Drelease-notes-4.0.rst58 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.
246 * Made these changes in other SoC series:
341 * Made these board changes:
431 documentation when changes to the input ``.rst`` files are detected on the filesystem.
580 * PHY driver changes
603 state changes and SPI transfers between other operations, specifically when burst type
1299 * No significant changes in this release
1318 * LittleFS: The module has been updated with changes committed upstream
Drelease-notes-2.5.rst20 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 …]
Drelease-notes-1.7.rst25 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.
Drelease-notes-3.1.rst8 The following sections provide detailed lists of changes by component.
167 Stable API changes in this release
309 changes. This prevents IPI "storms" with code that does many
367 * Made these changes in other SoC series:
400 * Made these changes in other boards:
682 * Multiple minor fixes/improvements to align with upstream OpenThread changes.
785 backwards incompatible changes affecting users of the old bindings. These
786 changes include:
1572 * :github:`44261` - twister: some changes make test cases work abnormally.
1646 * :github:`43818` - lib: os: ring_buffer: recent changes cause UART shell to fail on qemu_cortex_a9
[all …]
Dmigration-guide-3.6.rst8 This document describes the changes required when migrating your application from Zephyr v3.5.0 to
11 Any other changes (not directly related to migrating applications) can be found in
541 * The CoAP public API has some minor changes to take into account. The
/Zephyr-latest/doc/hardware/peripherals/can/
Dcontroller.rst101 the node changes to error-passive state.
103 If the transmit-error counter increases further to 255, the node changes to the
/Zephyr-latest/cmake/linker/armlink/
Dscatter_script.cmake424 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/cmake/modules/
Dkconfig.cmake13 # Re-configure (Re-execute all CMakeLists.txt code) when autoconf.h changes
410 # Force CMAKE configure when the Kconfig sources or configuration files changes.
/Zephyr-latest/doc/connectivity/usb/device_next/
Dusb_device.rst150 :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/services/portability/posix/overview/
Dindex.rst25 POSIX conformant can be ported to Zephyr kernel based applications with no changes.
/Zephyr-latest/
DCODE_OF_CONDUCT.md125 The only changes made by The Zephyr Project to the original document were to
/Zephyr-latest/doc/develop/west/
Dbuilt-in.rst10 on the entire workspace. For example, ``west diff`` shows local changes in
161 ignore incoming changes for the moment.
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_mgmt.rst18 a network interface IP address changes.
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dcore.rst76 device configuration persistently. When the stack configuration changes and
/Zephyr-latest/boards/nxp/rd_rw612_bga/doc/
Dindex.rst126 connected via jumper wires. Connections and required board changes are
/Zephyr-latest/doc/build/cmake/
Dindex.rst18 most code changes. However, after certain changes, the configuration step must
/Zephyr-latest/doc/develop/
Denv_vars.rst75 your changes by clicking the Save button at top left before exiting. Settings
/Zephyr-latest/doc/develop/application/
Dindex.rst61 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
914 Application development is usually fastest when changes are continually tested.
917 rebuild and test after any major changes to the application's source files,
923 potentially affected by the changes. Consequently, rebuilding an application
/Zephyr-latest/doc/security/
Dreporting.rst154 to determine if they need to backport these changes to any internal
/Zephyr-latest/doc/services/input/
Dgpio-kbd.rst240 changes, and once disabled it prints an or-mask of any key that has been
/Zephyr-latest/arch/xtensa/core/
DREADME_MMU.txt260 mapped. Page table changes in the data cache of one CPU will be
262 notifying another CPU of changes to page mappings beyond doing

12345678