From: Alexander Aring <alex.aring@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org, Ashutosh Singh <embedded.ashu@gmail.com>
Subject: Re: Can i access the barebox env from linux
Date: Wed, 26 Mar 2014 07:57:36 +0100 [thread overview]
Message-ID: <20140326065734.GA18805@omega.Speedport_W_921V_1_24_000> (raw)
In-Reply-To: <20140326062619.GP17250@pengutronix.de>
Hi Sascha and Ashutosh,
On Wed, Mar 26, 2014 at 07:26:19AM +0100, Sascha Hauer wrote:
> On Wed, Mar 26, 2014 at 11:25:07AM +0530, Ashutosh Singh wrote:
> > Dear All,
> >
> > Can i access the barebox env from linux.
> > Once the kernel boot if i want to create a directory and store some parameter
> > in default barebox /env folder without going to barebox from kernel.
> > For Eg.
> > I booted the board i get the linux promt and depending on some condition
> > i want to update the barebox env and create a directory in /env so the
> > next time
> > when barebox is loading the kernel image it can check that directory
> > and according
> > to that it can select the kernel from any source such as mmc, nand, nor, tftp.
> >
> > What i observe that after the kernel boot i can see the barebox.env is
> > mounted as mtdblock5 (case of Nand)
> > now according to my understanding can i mount this partition modify
> > with my custom directory
> > and again boot so that this directory is available in barebox /env .
>
> There is no filesystem support for the barebox environment, but you can
> access the barebox env under Linux using the bareboxenv tool. Enable
> [x] build bareboxenv tool for target
> and you'll find the tool under scripts/
>
I wrote fast some skript to handle a automatic write of the bareboxenv On
env changes. It use inotify to detect changes at the environment.
--- snip
#!/bin/sh
MNT=$1
ENV=$2
bareboxenv -l $MNT $ENV
while true
do
inotifywait -e modify $MNT --excludei ".*.swp"
bareboxenv -s $MNT $ENV
done
--- snap
NOTE: Don't use this on nand partitions!
This script can be run as daemon on the target and will automatic write
the environment back. Usage: "./script $MNTPOINT $BBENV".
I hacked this in 10 seconds but it depends if it a mtd device then we
should use nandwrite etc... but maybe we can write a proper C
implementation, with inotify, mtd ioctl calls (if mtd), etc...
I mean this would be very easy to implemented. :-)
- Alex
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-03-26 6:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 5:55 Ashutosh Singh
2014-03-26 6:26 ` Sascha Hauer
2014-03-26 6:57 ` Alexander Aring [this message]
2014-03-26 11:14 ` Ashutosh Singh
2014-03-26 11:31 ` Alexander Aring
2014-03-26 11:33 ` Alexander Aring
2014-03-26 11:53 ` Michel Stam
2014-03-26 11:58 ` Alexander Aring
2014-03-26 12:14 ` Michel Stam
[not found] ` <CA+dawz2HSTYcR4Lv_0Q_ECELh2i9kq6vnZTEdnD8e+qu4pyamA@mail.gmail.com>
[not found] ` <20140328091854.GA20774@omega.Speedport_W_921V_1_24_000>
[not found] ` <CA+dawz3gfhFv3mtAOjXVoooE5WqJb6sH1qbMmPw--OD-p_N4Qg@mail.gmail.com>
[not found] ` <20140328095241.GB21559@omega.Speedport_W_921V_1_24_000>
2014-03-31 0:12 ` Alexander Aring
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=20140326065734.GA18805@omega.Speedport_W_921V_1_24_000 \
--to=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=embedded.ashu@gmail.com \
--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