From: "Balasa, Bogdan" <BBalasa@Morganschaffer.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: barebox env userspace
Date: Tue, 4 Feb 2014 14:14:17 +0000 [thread overview]
Message-ID: <4C598A31AEBE214FB619D7F2DC3BD8AB0127A14BF9@MSI0E01.MSI.Local> (raw)
In-Reply-To: <20140204071748.GP16215@pengutronix.de>
Hi,
Is not working when modifying in userspace the '/init/general' file, the line:
'global.boot.default=nand'
to: 'global.boot.default=two'
and after reset barebox was not taking into account this change.
I needed to enter in barebox abd send a saveenv in barebox such that the content of '/init/general'
to be saved in the persistent storage (I think dev/env0).
-----Message d'origine-----
De : Sascha Hauer [mailto:s.hauer@pengutronix.de]
Envoyé : February-04-14 2:18 AM
À : Balasa, Bogdan
Cc : barebox@lists.infradead.org
Objet : Re: barebox env userspace
On Mon, Feb 03, 2014 at 06:00:02PM +0000, Balasa, Bogdan wrote:
> I was modifying the '/init/general' file, the line:
>
> global.boot.default=nand
>
> A second method (this one worked): changed the content of 'boot/nand' file.
>
> Bogdan
>
> -----Message d'origine-----
> De : Balasa, Bogdan [mailto:BBalasa@Morganschaffer.com]
> Envoyé : February-03-14 12:20 PM
> À : barebox@lists.infradead.org
> Objet : barebox env userspace
>
> Hi,
>
> I try to modify the barebox environment from linux userspace with:
>
> 1. Load environment from SPI NOR flash:
> ./bareboxenv-target -l /mnt /dev/mtd1
>
> 2. Erase environment from SPI nor flash
> flash_erase /dev/mtd1 0 0
>
> # do some modifications in "/mnt"
>
> 3. Save environment to NOR flash
> ./bareboxenv-target -s /mnt /dev/mtd1
>
> ----
> After reset I can see my modifications in the files within barebox but the changes are not taken into account by barebox.
So it doesn't seem to be a problem with accessing/changing the environment from userspace, but that you modify a file which isn't used by barebox, or not used as you are expecting it. What file are you modifying?
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:[~2014-02-04 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 17:19 Balasa, Bogdan
2014-02-03 18:00 ` Balasa, Bogdan
2014-02-04 7:17 ` Sascha Hauer
2014-02-04 14:14 ` Balasa, Bogdan [this message]
2014-02-05 8:18 ` Sascha Hauer
2014-02-05 15:42 ` Balasa, Bogdan
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=4C598A31AEBE214FB619D7F2DC3BD8AB0127A14BF9@MSI0E01.MSI.Local \
--to=bbalasa@morganschaffer.com \
--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