From: John Stile <john@stilen.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Can I read env from RAM in uboot script?
Date: Mon, 28 Jan 2013 13:19:05 -0800 [thread overview]
Message-ID: <1359407945.7974.144.camel@genx> (raw)
In-Reply-To: <20130126074103.AD5232005C3@gemini.denx.de>
On Sat, 2013-01-26 at 08:41 +0100, Wolfgang Denk wrote:
> Dear John Stile,
>
> In message <1359165410.7974.114.camel@genx> you wrote:
> > Is it possible to have uboot read it's environment from a RAM address,
> > rather than NAND?
> > OR
> > Can uboot's scripting support load variables from a RAM address?
>
> Yes, all this can be done. And easily. See for example the
> "env import" command.
>
That is a great idea.
What version of uboot introduced 'env import'?
I'm stuck on u-boot-1.3.4.
Is there a patch?
next prev parent reply other threads:[~2013-01-28 21:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 1:56 [U-Boot] Can I read env from RAM in uboot script? John Stile
2013-01-26 7:41 ` Wolfgang Denk
2013-01-28 21:19 ` John Stile [this message]
2013-01-28 21:48 ` Jeroen Hofstee
2013-01-28 22:01 ` Jeroen Hofstee
2013-01-29 0:25 ` John Stile
2013-01-29 9:58 ` Bo Shen
2013-01-29 17:33 ` John Stile
2013-01-30 1:20 ` Bo Shen
2013-01-29 6:37 ` Wolfgang Denk
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=1359407945.7974.144.camel@genx \
--to=john@stilen.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