From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot USB question
Date: Fri, 17 May 2013 07:54:33 +0200 [thread overview]
Message-ID: <5195C619.90008@googlemail.com> (raw)
In-Reply-To: <E632120D9F6D2B4C992D00A695B685CD0C493CE968@P3PW5EX1MB09.EX1.SECURESERVER.NET>
Hi Lance,
please do not top post.
On 17.05.13 04:20, Lance Beck wrote:
> Thanks Bo!
>
> My thinking with fw_printev (setenv) was that I would use it to set the environment variables
> from our user space app.
That's the intended use of fw_setenv ;)
> This way, we can control when the USB stick will be used for a kernel
> or rootfs upgrade. Any thoughts on show this could be scripted and run?
As Bo mentioned. But why don't just do this in userspace?
First thing would be to have a script that stops services, remount
everything ro and write the respective blobs to /dev/mtdX.
Another solution (or enhancement) could be to spawn a kexec kernel and
do all the stuff in a clean environment.
The advantage of this solution is to have a full blown environment with
sophisticated UI. I think this is the most annoying thing in u-boot ...
we do lack a good environment for UI represented to the end user. Well,
we have to discuss if this is a drawback ;)
Best regards
Andreas Bie?mann
next prev parent reply other threads:[~2013-05-17 5:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 22:32 [U-Boot] u-boot USB question Lance Beck
2013-05-17 1:22 ` Bo Shen
2013-05-17 2:20 ` Lance Beck
2013-05-17 3:04 ` Bo Shen
2013-05-17 3:39 ` Michael Trimarchi
2013-05-17 5:54 ` Andreas Bießmann [this message]
2013-05-17 5:45 ` Andreas Bießmann
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=5195C619.90008@googlemail.com \
--to=andreas.devel@googlemail.com \
--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