Searched full:modifications (Results 1 – 25 of 53) sorted by relevance
123
/Zephyr-Core-3.6.0/ |
D | LICENSE | 26 "Source" form shall mean the preferred form for making modifications, 42 editorial revisions, annotations, elaborations, or other modifications 49 the original version of the Work and any modifications or additions 91 modifications, and in Source or Object form, provided that You 123 You may add Your own copyright statement to Your modifications and 125 for use, reproduction, or distribution of Your modifications, or
|
/Zephyr-Core-3.6.0/boards/shields/x_nucleo_idb05a1/doc/ |
D | index.rst | 47 Additionally, depending on your host board, some modifications of the BLE 55 The stm32mp157c_dk2 board is known to need those CS/IRQ pin modifications 57 whereas nucleo_l476rg doesn't need hardware modifications.
|
/Zephyr-Core-3.6.0/kernel/include/ |
D | gen_offset.h | 19 * Consequently, changes made to such symbols may require modifications to the 24 * changing the meaning of an absolute symbol may require modifications to a
|
/Zephyr-Core-3.6.0/boards/shields/x_nucleo_bnrg2a1/doc/ |
D | index.rst | 43 Additionally, depending on your host board, some modifications of the BLE 48 nucleo_l476rg does not need hardware modifications.
|
/Zephyr-Core-3.6.0/tests/drivers/build_all/fpga/ |
D | app.overlay | 43 /* Put device specific modifications to properties or disabling of devices
|
/Zephyr-Core-3.6.0/.github/ISSUE_TEMPLATE/ |
D | 003_rfc-proposal.md | 42 modifications in other areas), or other teams/projects.
|
/Zephyr-Core-3.6.0/boards/arm/stm32h747i_disco/doc/ |
D | index.rst | 142 `DISCO_H747I modifications for Ethernet`_ mbed blog post. The author of this 144 HW modifications to get Ethernet working with this board. 146 To get Ethernet working following HW modifications are required: 309 .. _DISCO_H747I modifications for Ethernet: 310 https://os.mbed.com/teams/ST/wiki/DISCO_H747I-modifications-for-Ethernet
|
/Zephyr-Core-3.6.0/dts/bindings/pinctrl/ |
D | nuvoton,numaker-pinctrl.yaml | 13 /* your modifications go here */
|
D | renesas,rzt2m-pinctrl.yaml | 13 /* your modifications go here */
|
D | ite,it8xxx2-pinctrl.yaml | 14 /* your modifications go here */
|
D | ambiq,apollo4-pinctrl.yaml | 13 /* your modifications go here */
|
D | silabs,gecko-pinctrl.yaml | 14 /* your modifications go here */
|
D | renesas,rcar-pfc.yaml | 16 /* your modifications go here */
|
D | renesas,smartbond-pinctrl.yaml | 13 /* your modifications go here */
|
D | telink,b91-pinctrl.yaml | 14 /* your modifications go here */
|
D | atmel,sam-pinctrl.yaml | 17 /* your modifications go here */
|
D | ti,cc32xx-pinctrl.yaml | 14 /* your modifications go here */
|
D | ti,cc13xx-cc26xx-pinctrl.yaml | 15 /* your modifications go here */
|
D | raspberrypi,pico-pinctrl.yaml | 14 /* your modifications go here */
|
D | atmel,sam0-pinctrl.yaml | 17 /* your modifications go here */
|
D | infineon,cat1-pinctrl.yaml | 18 /* Your modifications go here */
|
D | microchip,xec-pinctrl.yaml | 16 /* your modifications go here */
|
D | gd,gd32-pinctrl-af.yaml | 14 /* your modifications go here */
|
D | nordic,nrf-pinctrl.yaml | 14 /* your modifications go here */
|
/Zephyr-Core-3.6.0/doc/hardware/peripherals/ |
D | i3c.rst | 307 API can accommodate I2C API calls without modifications if the controller 309 existing I2C devices without any modifications to their device drivers. 326 device drivers can be used as-is without modifications. This requires
|
123