From: "Boulais, Marc-Andre" <maboulais@rheinmetall.ca>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: Specify where to save Barebox env
Date: Thu, 19 Feb 2015 20:32:54 +0000 [thread overview]
Message-ID: <29A2697B0516A946B1023D5E798DFCF67BACD8E7@mail-yang> (raw)
In-Reply-To: <20150219200836.GB12209@pengutronix.de>
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 ?
-----Original Message-----
From: Sascha Hauer [mailto:s.hauer@pengutronix.de]
Sent: February-19-15 3:09 PM
To: Boulais, Marc-Andre
Cc: barebox@lists.infradead.org
Subject: Re: Specify where to save Barebox env
On Wed, Feb 18, 2015 at 07:55:46PM +0000, Boulais, Marc-Andre wrote:
> Good day,
> I am working on a phytec-phycore-OMAP446 system where the system
> boots from the SD card. On it, I have MLO+barebox.bin (v2015.02). The
> system boots ok. However, when I set NV variables (from its prompt)
> and then do a "saveenv", I would like the environment to be saved in
> NAND. Is there a way to configure Barebox to do that ?
Normally barebox stores the environment on the medium it is started from. Looking at arch/arm/boards/phytec-phycore-omap4460/board.c:
#ifdef CONFIG_PARTITION
devfs_add_partition("nand0", 0x00000, SZ_128K, DEVFS_PARTITION_FIXED, "xload_raw");
dev_add_bb_dev("xload_raw", "xload");
devfs_add_partition("nand0", SZ_128K, SZ_512K, DEVFS_PARTITION_FIXED, "self_raw");
dev_add_bb_dev("self_raw", "self0");
devfs_add_partition("nand0", SZ_128K + SZ_512K, SZ_128K, DEVFS_PARTITION_FIXED, "env_raw");
dev_add_bb_dev("env_raw", "env0"); #endif
The last two lines create /dev/env0 on nand. If you boot from nand the environment should be stored there already.
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:[~2015-02-19 20:33 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 [this message]
2015-02-19 21:16 ` 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=29A2697B0516A946B1023D5E798DFCF67BACD8E7@mail-yang \
--to=maboulais@rheinmetall.ca \
--cc=barebox@lists.infradead.org \
--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