Searched refs:changes (Results 26 – 50 of 191) sorted by relevance
12345678
| /Zephyr-latest/tests/drivers/gpio/gpio_basic_api/boards/ |
| D | intel_ehl_crb.overlay | 7 * Please follow up do the following changes:
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | ethernet_mgmt.rst | 28 when the corresponding status changes.
|
| D | net_if.rst | 79 changes).
86 event that changes the carrier state is Ethernet cable being plugged in or out.
91 initialized interface. An example of an event that changes the dormant state is
|
| /Zephyr-latest/doc/services/debugging/ |
| D | cs_trace_defmt.rst | 17 :c:func:`cs_trace_defmt_process` in 16 bytes chunks. Callback is called whenever stream changes or
|
| /Zephyr-latest/tests/drivers/clock_control/stm32_clock_configuration/stm32_common_devices/boards/ |
| D | g4_i2c1_hsi_adc1_pllp.overlay | 70 /* changes clock source for both ADC1 and ADC2 */
|
| /Zephyr-latest/tests/benchmarks/sched_queues/ |
| D | Kconfig | 22 differences as the number of threads in the ready queue changes.
|
| /Zephyr-latest/tests/benchmarks/wait_queues/ |
| D | Kconfig | 22 differences as the number of threads in the wait queue changes.
|
| /Zephyr-latest/cmake/modules/ |
| D | snippets.cmake | 39 # Warn the user if SNIPPET changes later. Such changes are ignored.
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 32 #. The Zephyr Safety Committee will review these changes and provide feedback or acceptance of
33 the changes.
35 #. Once accepted, these changes will become part of the document.
170 faulty changes and further minimizing the error rate. However, it must be noted that different
246 and decisions of minor changes in the safety scope to be able to react to safety-relevant
247 changes that are not conformant. If a pull request or issue introduces a significant and
254 "auditable" state, and ideally no further changes should be necessary or made to the code base.
273 a path to merge these changes back into the main branch so that they are not lost, and to have
|
| /Zephyr-latest/subsys/logging/ |
| D | CMakeLists.txt | 26 # - GCC 4.9.0 https://gcc.gnu.org/gcc-4.9/changes.html
|
| /Zephyr-latest/scripts/ci/es_upload/ |
| D | README.md | 11 Besides, it allows to track changes in Twister JSON report scheme
20 Use these examples as a reference for your setup. Always pay attention to possible changes
55 * `--flatten` changes testsuite data structure in regard of one of its list components:
|
| /Zephyr-latest/samples/boards/nordic/dynamic_pinctrl/ |
| D | README.rst | 13 Slightly different board revisions that implement just small changes (like
15 necessarily require changes to the firmware. As such, one firmware image can be
|
| /Zephyr-latest/scripts/dts/ |
| D | README.txt | 23 repository. We will mirror changes into the standalone repository as
|
| /Zephyr-latest/subsys/net/ |
| D | Kconfig.hostname | 46 This will update the unique hostname on link address changes. By
|
| /Zephyr-latest/drivers/input/ |
| D | Kconfig.kbd_matrix | 32 bool "Allow runtime changes to the actual key mask"
|
| /Zephyr-latest/samples/drivers/display/ |
| D | README.rst | 14 grey changes from black through to white. If the grey looks too green or red
|
| /Zephyr-latest/doc/project/ |
| D | release_process.rst | 26 changes such as bug fixes and documentation will be merged unless granted a
29 - Development phase: all changes are considered and merged, subject to
61 merged into the mainline tree. The bulk of changes for a new development cycle
62 (and all of the major changes) will be merged during this time.
76 cosmetic changes, tests, bug and doc fixes are allowed (See :ref:`table
79 On occasion, more significant changes and new features will be allowed, but such
176 - No new features after RC1, ONLY stabilization and cosmetic changes, bug and doc
181 …- No new features after RC2, ONLY stabilization and cosmetic changes, bug and doc fixes are allowe…
185 - Only blocker bug fixes after RC3, documentation and changes to release notes are allowed.
339 Changes and fixes flow in both directions. However, changes from main branch to an
|
| D | index.rst | 26 **Pull Requests** (PRs) for submitting and reviewing changes. Zephyr
|
| /Zephyr-latest/samples/sensor/qdec/ |
| D | README.rst | 66 Of course the read value changes once the user manually rotates the mechanical
|
| /Zephyr-latest/doc/services/resource_management/ |
| D | index.rst | 71 changes, including when a service begins turning off or enters an error
73 with onoff_monitor_register(). Notification of changes are provided
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-4.1.rst | 12 An overview of the changes required or recommended when migrating your application from Zephyr
15 The following sections provide detailed lists of changes by component.
109 * Made these changes in other SoC series:
116 * Made these board changes:
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | charger.rst | 18 environmental changes.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfd_srv.rst | 31 and delete old ones. The application is notified of changes to the slots through the Firmware
|
| D | priv_beacon_srv.rst | 28 changes to this configuration in the settings subsystem, the initial values may
|
| /Zephyr-latest/ |
| D | CONTRIBUTING.rst | 6 standards and methods for submitting changes help reduce the chaos that can result
|
12345678
