From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] user-space ===>> U-Boot ====>> user-space ?
Date: Tue, 12 Oct 2010 07:16:30 +0200 [thread overview]
Message-ID: <20101012051630.8909214F310@gemini.denx.de> (raw)
In-Reply-To: <29939469.post@talk.nabble.com>
Dear bosmith,
In message <29939469.post@talk.nabble.com> you wrote:
>
> Is there a simple way to send data from a Linux user-space program to
> U-Boot?
> How about from U-Boot up to a user-space program?
I know of two communication methods:
Using the environment (and fw_printenv/fw_setenv in Linux user space),
and using a shared log buffer (which may be a bit difficult to read /
process in U-Boot if that should be needed).
> The data may change often enough that using fw_printenv and fw_setenv might
> wear out the NAND storage area for the environment.
Then put all this stuff in a UBI partition, and use the "env import" /
"env export" features in U-Boot to access it (or extend the code to
handle environment in a UBI partition directly).
> The use-case is to have two kernel images, two root file systems, and to let
> a user-space application specify which to use and then force a reboot. The
> system will not lose power during this reboot.
And you think you will switch betweent these two so often that using
the environment would wear out the NAND? I think you are too
pessimistic.
> This seems like a common enough problem. Has anyone solved it before?
Most people use the environment for this purpose.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Today is the yesterday you worried about tomorrow.
next prev parent reply other threads:[~2010-10-12 5:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 1:44 [U-Boot] user-space ===>> U-Boot ====>> user-space ? bosmith
2010-10-12 5:16 ` Wolfgang Denk [this message]
2010-10-12 22:18 ` Swarthout Edward L-SWARTHOU
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=20101012051630.8909214F310@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.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