public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jeroen Hofstee <jeroen@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] Can I read env from RAM in uboot script?
Date: Mon, 28 Jan 2013 23:01:13 +0100	[thread overview]
Message-ID: <5106F529.2030407@myspectrum.nl> (raw)
In-Reply-To: <5106F224.8010601@myspectrum.nl>


> On 01/28/2013 10:19 PM, John Stile wrote:
>> 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?
>>
> search the mailinglist, this is asking for a visit to
> http://www.uboat.net/special/archiv/ or a response the
> like. Try to upgrade if possible...

for completeness sake, Wolfgang will likely tell you it is museum material,
since it is almost 5 years old. No idea what the site is about, just popped
up with "u-boot museum" instead of Wolfgang's replies.

Regards,
Jeroen

  reply	other threads:[~2013-01-28 22:01 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
2013-01-28 21:48     ` Jeroen Hofstee
2013-01-28 22:01       ` Jeroen Hofstee [this message]
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=5106F529.2030407@myspectrum.nl \
    --to=jeroen@myspectrum.nl \
    --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