Searched refs:change (Results 101 – 125 of 327) sorted by relevance
12345678910>>...14
/Zephyr-latest/samples/net/ipv4_autoconf/ |
D | README.rst | 64 Note that the IP address may change at each self assignment.
|
/Zephyr-latest/subsys/net/ip/ |
D | Kconfig.mgmt | 9 events (ip address change, iface up and running ...). 18 (ip address change for instance) to trigger some related work.
|
/Zephyr-latest/doc/releases/ |
D | index.rst | 121 Each entry in the migration guide must include a brief explanation of the change 123 to be able to understand the context of the change.
|
D | migration-guide-3.5.rst | 57 You can change this by adjusting 116 required change in the DT: 134 be used instead. This change is due to a limitation on STM32F4 where the 179 compatible declaration. You may update an existing sh1106 node to change the 195 will see last 3 bytes of their MAC address modified by this change. 264 :kconfig:option:`CONFIG_PM`. Before this change all platforms could enable 266 this is no longer supported. As a result of this change, power management
|
/Zephyr-latest/samples/boards/nordic/mesh/onoff-app/ |
D | README.rst | 28 also publish its status on an onoff state change. 92 change the state of any LED that is bound to application key 0x1.
|
/Zephyr-latest/drivers/sensor/st/lis2dw12/ |
D | Kconfig | 71 Enable sleep (inactivity) mode with ODR change when detected
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | sdhc.rst | 38 The :c:func:`sdhc_set_io` api allows the user to change I/O settings of the SD
|
/Zephyr-latest/samples/subsys/ipc/ipc_service/multi_endpoint/ |
D | README.rst | 67 To change the backend to ``icbmsg``, switch the devicetree
|
/Zephyr-latest/subsys/ |
D | Kconfig | 67 this option alone doesn't change the build on its own, it only allows
|
/Zephyr-latest/subsys/input/ |
D | Kconfig | 45 Option to change the default value of input thread priority.
|
/Zephyr-latest/boards/intel/ehl/doc/ |
D | index.rst | 83 change boot order
|
/Zephyr-latest/samples/kernel/condition_variables/condvar/ |
D | README.rst | 32 To build for another board, change ``native_sim`` above to that board's name.
|
/Zephyr-latest/samples/drivers/adc/adc_dt/ |
D | README.rst | 49 To build for another board, change "nucleo_l073rz" above to that board's name
|
/Zephyr-latest/samples/drivers/adc/adc_sequence/ |
D | README.rst | 42 To build for another board, change "nrf52840dk/nrf52840" above to that board's name
|
/Zephyr-latest/tests/drivers/i2c/i2c_target_api/ |
D | README.txt | 6 plans to change the terminology used in this API.
|
/Zephyr-latest/samples/bluetooth/channel_sounding/ |
D | README.rst | 130 …wp-content/uploads/Files/Specification/HTML/Core-60/out/en/architecture,-change-history,-and-conve… 131 …wp-content/uploads/Files/Specification/HTML/Core-60/out/en/architecture,-change-history,-and-conve…
|
/Zephyr-latest/boards/shields/x_nucleo_wb05kn1/doc/ |
D | index.rst | 42 Please, bear in mind in order to use SPI interface you need to change the shield firmware
|
/Zephyr-latest/samples/tfm_integration/tfm_secure_partition/ |
D | README.rst | 28 When adapting this partition for your own purposes, please change all occurrences of
|
/Zephyr-latest/ |
D | .gitlint | 59 # By specifying this rule, developers can only change the file when they explicitly reference
|
/Zephyr-latest/cmake/ |
D | target_toolchain_flags.cmake | 7 # the MD5 will also change (as example toolchain upgrade in same folder)
|
/Zephyr-latest/samples/boards/st/sensortile_box/ |
D | README.rst | 83 sensor, you will see the accelerometer, gyro, and temperature values change.
|
/Zephyr-latest/arch/xtensa/core/ |
D | README_MMU.txt | 214 context switch time, you can simply change RADID and the page table 221 stored at ASID 1 (ring 0), they can't change when the page tables 222 change! So this region naively would have to be flushed, which is 234 Note, obviously, that any change of the mappings within an ASID 236 mapping change other than mapping previously-unmapped pages) still 248 page mapped within the same cache line, or to change the tables) then
|
/Zephyr-latest/doc/safety/ |
D | safety_overview.rst | 275 change is related to safety. 288 influential change or improvement that requires extended discussion or decision-making, the 296 important change is found or implemented on the main branch in the safety scope, after the LTS 298 safety architect, must decide whether this bug fix or change should be integrated into the LTS 299 so that the bug fix or change could also be integrated into the auditable branch. This 300 integration can take three forms: First either as only a code change or second as only an update
|
/Zephyr-latest/scripts/ci/es_upload/ |
D | README.md | 44 The upload script has several command line options to change `twister.json` data: 45 exclude excess data, extract substrings by regular expressions, change data structure
|
/Zephyr-latest/boards/xen/xenvm/doc/ |
D | index.rst | 68 hardware you might want to change this option in the same way as Interrupt 166 will not change some values (like RAM base address) in the future.
|
12345678910>>...14