From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: how does barebox deal with more than one environment?
Date: Sat, 1 Dec 2012 09:07:53 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1212010906080.13744@oneiric> (raw)
In-Reply-To: <CAA4bVAHj_Q12r087kYOvwXj+9vRb1cFANa7nMUKTQzH+qmmEAw@mail.gmail.com>
On Sat, 1 Dec 2012, Antony Pavlov wrote:
> On 1 December 2012 17:19, Robert P. J. Day <rpjday@crashcourse.ca> 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.
>
> See common/startup.c:110
>
> #ifdef CONFIG_ENV_HANDLING
> if (envfs_load(default_environment_path, "/env")) {
> #ifdef CONFIG_DEFAULT_ENVIRONMENT
> printf("no valid environment found on %s. "
> "Using default environment\n",
> default_environment_path);
> envfs_load("/dev/defaultenv", "/env");
> #endif
>
> By default default_environment_path="/dev/env0", but it can be
> overwritten in a board code (e.g. see arch/arm/boards/panda/board.c).
i realize that -- what i was asking about were the possible
*additional* environments (/dev/env1, /dev/env2, ...) that are
mentioned on that page.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-12-01 14:07 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 [this message]
2012-12-03 9:04 ` Sascha Hauer
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=alpine.DEB.2.02.1212010906080.13744@oneiric \
--to=rpjday@crashcourse.ca \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
/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