[coreboot] How to best add new boards derived from existing board?
paulepanter at users.sourceforge.net
Sun Sep 29 23:16:51 CEST 2013
Dear coreboot folks,
it is great to see patches adding new boards to our repository. Lately
this was AMD Olive Hill , ASRock IMB-A180  and just now the Micro
Passion Kratos-X1 .
The Olive Hill took a AMD Family 15 board as a template, the IMB-A180
was derived from the Olive Hill and, I believe, the Kratos-X1 is also
derived from one of these two. (Derived means, an existing board’s
directory was copied and then adapted.)
With the current approach it is difficult to see the actual changes to
the template board. Especially in Gerrit. Therefore these board support
patches are hard to review.
Do you know, how to avoid this problem? Currently, I came only up with
adding a “copy-commit” with just the Kconfig name changes and then the
actual changes in a separate commit on top of it. Jens Rottmann did the
same when adding the LiPPERT (now ADLINK) boards .
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: This is a digitally signed message part
More information about the coreboot