Browse Source
With the support of omitting SoC field for single SoC boards then there is no reason to have this field optional. Users are still able to use a short board name when building. But always requiring SoC field in the board.yml paves the way for future enhancements to the new hw model without having to do a second update to a lot of board.yml files. Such enhancement can be: - Create Kconfig SoC selection and thereby remove need for Kconfig boilerplate code, and also thereby remove risk of naming inconsistencies. - Extend board documentation, so that web doc provides option to filter all boards with a given SoC. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>pull/69687/head
1 changed files with 1 additions and 3 deletions
Loading…
Reference in new issue