Searched refs:VENDOR (Results 1 – 6 of 6) sorted by relevance
| /Zephyr-latest/doc/hardware/porting/ |
| D | soc_porting.rst | 42 Start by creating the directory ``zephyr/soc/<VENDOR>/soc1``, where
43 ``<VENDOR>`` is your vendor subdirectory.
46 A ``<VENDOR>`` subdirectory is mandatory if contributing your SoC
49 The ``<VENDOR>`` subdirectory must match a vendor defined in the list in
63 soc/<VENDOR>/<soc-name>
149 under a corresponding :file:`<ARCH>/<VENDOR>`.
151 The SoC :file:`dts/<ARCH>/<VENDOR>/<soc>.dtsi` describes your SoC hardware in
186 It is possible to structure multiple :file:`<VENDOR>/<soc>.dtsi` files in
188 pre SoC series, like this: :file:`<VENDOR>/<SERIES>/<soc>.dtsi`.
|
| D | board_porting.rst | 219 add it in a new directory ``zephyr/soc/<VENDOR>/<YOUR-SOC>``; please use
235 Start by creating the board directory ``zephyr/boards/<VENDOR>/plank``, where
236 ``<VENDOR>`` is your vendor subdirectory. (You don't have to put your
242 A ``<VENDOR>`` subdirectory is mandatory if contributing your board
247 that vendor prefix as ``<VENDOR>``. ``others`` may be used as vendor prefix if
259 boards/<VENDOR>/plank
953 boards/<VENDOR>/plank
967 boards/<VENDOR>/plank
|
| /Zephyr-latest/scripts/ |
| D | list_boards.py | 426 VENDOR='VENDOR;' + notfound(b.vendor),
452 VENDOR='VENDOR;NOTFOUND',
|
| D | list_hardware.py | 290 VENDOR=''
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | setting.rst | 131 :file:`boards/<VENDOR>/<BOARD>/<BOARD>_defconfig`
255 :file:`boards/<VENDOR>/<BOARD>/Kconfig.defconfig`, which is a regular
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-4.0.rst | 648 * Added helper functions for sending CCCs for ENTTM, VENDOR, DEFTGTS, SETAASA,
650 * Added shell commands for sending CCCs for ENTTM, VENDOR, DEFTGTS, SETAASA,
|
