From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Boulais, Marc-Andre" <maboulais@rheinmetall.ca>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Specify where to save Barebox env
Date: Thu, 19 Feb 2015 22:16:55 +0100 [thread overview]
Message-ID: <20150219211655.GE12209@pengutronix.de> (raw)
In-Reply-To: <29A2697B0516A946B1023D5E798DFCF67BACD8E7@mail-yang>
On Thu, Feb 19, 2015 at 08:32:54PM +0000, Boulais, Marc-Andre wrote:
> The system I am working on requires to boot from the SD card. However,
> the Linux application needs to have the ability to change boot
> parameters to set the location of the kernel and rootfs for the next
> boot. I was planning on making the Linux application use the
> bareboxenv-target tool to map the Barebox environment and then modify
> variables accordingly.
>
> From what I understand, this is possible when the environment is in
> NAND. Is it also true if the env. is on the SD card (barebox.env file)
> ? if so, how is it done ?
You have to mount the partition containing the environment before using
the bareboxenv tool.
BTW you to always store the environment on Nand you would have to
comment out the omap_env_init function.
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
prev parent reply other threads:[~2015-02-19 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 19:55 Boulais, Marc-Andre
2015-02-19 20:08 ` Sascha Hauer
2015-02-19 20:32 ` Boulais, Marc-Andre
2015-02-19 21:16 ` Sascha Hauer [this message]
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=20150219211655.GE12209@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=maboulais@rheinmetall.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