From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: how does barebox deal with more than one environment?
Date: Mon, 3 Dec 2012 10:04:13 +0100 [thread overview]
Message-ID: <20121203090413.GH10369@pengutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1212010818090.13158@oneiric>
On Sat, Dec 01, 2012 at 08:19:26AM -0500, Robert P. J. Day wrote:
> On Sat, 1 Dec 2012, Robert P. J. Day wrote:
>
> >
> > writing up a simple barebox exercise for students and on this page:
> >
> > http://wiki.barebox.org/doku.php?id=user:first_steps
> >
> > it seems clear(?) that you can define multiple environments that will
> > appear at /dev/env0, /dev/env1, etc, but that page also claims that
> > *only* the configuration on /dev/env0 will be executed automatically
> > if barebox finds that it's a valid configuration sector.
> >
> > so what happens with the additional environments? that page doesn't
> > make it clear. i'm just about to read the source to see if i can
> > figure this out.
>
> oh, wait, i think i see ... the "loadenv" command will load a given
> environment into a directory so i'm *assuming* that additional
> environments are simply available to be loaded, but /dev/env0 is the
> only one treated special. or feel free to correct me if i'm
> hopelessly wrong.
/dev/env0 is the only environment used by barebox by default. As you
correctly found out loadenv/saveenv could be used to load arbitrary
envfs images to arbitrary directories. We could also think about
adding some kind of redundancy, but currently this would be board
specific, there is no generic heuristic to fall back to a second
env if the first one is corrupted.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-12-03 9:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-01 13:12 Robert P. J. Day
2012-12-01 13:19 ` Robert P. J. Day
2012-12-01 13:46 ` Antony Pavlov
2012-12-01 14:07 ` Robert P. J. Day
2012-12-03 9:04 ` Sascha Hauer [this message]
2012-12-03 12:48 ` Robert P. J. Day
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=20121203090413.GH10369@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rpjday@crashcourse.ca \
/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