From: Holger Schurig <holgerschurig@gmail.com>
To: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Fwd: Shouldn't boot_board be called from boot instead of init?
Date: Mon, 22 Aug 2016 11:46:53 +0200 [thread overview]
Message-ID: <87mvk5nnjm.fsf@gmail.com> (raw)
In-Reply-To: <CABDcavb3DN9Hc-Gr-vYG6aPHBgMYhM__4BzxVAjEqp5MdhB6qA@mail.gmail.com>
Guillermo Rodriguez Garcia <guille.rodriguez@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.
Hi,
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.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-08-22 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABDcavbrkt2q3cQ5Tzi3d0pU+Pm3v4S3OGzFo_aG_SNgmEgOnA@mail.gmail.com>
2016-08-16 8:42 ` Guillermo Rodriguez Garcia
2016-08-18 6:31 ` Sascha Hauer
2016-08-18 8:02 ` Guillermo Rodriguez Garcia
2016-08-22 5:45 ` Sascha Hauer
2016-08-22 9:12 ` Guillermo Rodriguez Garcia
2016-08-22 9:46 ` Holger Schurig [this message]
2016-08-23 8:13 ` Sascha Hauer
2016-08-24 14:42 ` Guillermo Rodriguez Garcia
2016-08-29 7:06 ` Sascha Hauer
2016-08-22 13:45 ` [PATCH] Call boot_board from boot, not from init Guillermo Rodriguez
2016-08-24 10:33 ` Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvk5nnjm.fsf@gmail.com \
--to=holgerschurig@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=guille.rodriguez@gmail.com \
--cc=s.hauer@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox