Fwd: Shouldn't boot_board be called from boot instead of init?
holgerschurig at gmail.com
Mon Aug 22 02:46:53 PDT 2016
Guillermo Rodriguez Garcia <guille.rodriguez at gmail.com> writes:
> With defaultenv-2 the "board configuration" is scattered through a
> number of tiny files, some of which contain just a single value (see
> for example nv/autoboot_timeout or nv/user). I find this more
> difficult to manage -- you need to edit a lot of tiny files instead of
> just one. Also I feel that the flow of control is less obvious for the
> same reason.
on my device I use defaultenv-1 for the same reason. Basically I just
have one env/bin/init and one env/config file and that's it. And the
env/config one is even so small that I could fold it into env/bin/init.
This even more so as my device is "set in stone", e.g. there is no SPI
EEPROM or other means (partition) to store an environment. What comes
with the compiled barebox is the environment.
Having things in one place and not scattered around makes things visible
at a glance.
More information about the barebox