From: Trent Piepho <tpiepho@kymetacorp.com>
To: "fhunleth@troodon-software.com" <fhunleth@troodon-software.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Accessing non-volatile variables from Linux
Date: Wed, 25 Jan 2017 20:51:43 +0000 [thread overview]
Message-ID: <1485377572.20042.51.camel@kymetacorp.com> (raw)
In-Reply-To: <CA+-urNQJbuE44V93+BERHf9r5kEKzn5mBJ5e=t9932TtR7+0Yw@mail.gmail.com>
On Wed, 2017-01-25 at 14:21 -0500, Frank Hunleth wrote:
> I'm wondering if it's possible to read and modify Barebox environment
> variables from Linux in a way similar to U-Boot's fw_printenv and
> fw_setenv. If that's not possible, is there another way for communicating
> between Linux and Barebox? Apologies if I totally missed a section in the
> docs that describes this.
This might not be useful for what you want, but it could be. Many SoCs
have "handoff" registers that don't have any predefined use and are
preserved across a soft reset.
You can write to the register(s) from Linux, then reboot to Barebox and
see the value, which could then trigger some action in Barebox.
Of course the registers are not preserved across a hard reset, which
might be a plus or minus depending on what you want to do.
This allows you to pass info to barebox without having to worry about
what happens if the env is corrupted while being modified. The barebox
env format is NOT a log based FS designed to prevent this!
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-01-25 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 19:21 Frank Hunleth
2017-01-25 20:51 ` Trent Piepho [this message]
2017-01-26 7:30 ` Sascha Hauer
2017-01-26 13:30 ` Frank Hunleth
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=1485377572.20042.51.camel@kymetacorp.com \
--to=tpiepho@kymetacorp.com \
--cc=barebox@lists.infradead.org \
--cc=fhunleth@troodon-software.com \
/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