If you refactor that code, could you make it easier to add the fallback? One of the main reason I use overlayfs is to keep a separate fallback

Overlayfs may remain a good option when working on separate source trees, but when the differences are just in the .config. it would be nice to specify the .config-fallback, the .config-normal, run make and get a coreboot.rom without having to manually give the file that needs to be updated. I wrote scripts to do just that.

On Sun, Nov 20, 2016 at 4:36 PM, ron minnich <rminnich@gmail.com> wrote:


On Sun, Nov 20, 2016 at 1:00 PM Matt DeVillier <matt.devillier@gmail.com> wrote:
On Sun, Nov 20, 2016 at 2:51 PM, ron minnich <rminnich@gmail.com> wrote:
I had the same thought even while writing that note. So option 2 for the config file is to create it at the top level: config.${MAINBOARD) or somewhere else. Would that work?

using top level for config files would really clutter the root dir when building for a large # of boards (I have ~25 I'm building for currently); perhaps a 'configs' subdir would make sense?   


yes, and the configs would go well in a .gitignore ... 

--
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot