From: Randy Smith <rsmith@imagemap.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Redundant environment expected behavior vs current
Date: Wed, 26 Apr 2006 09:25:05 -0400 [thread overview]
Message-ID: <444F74B1.8060909@imagemap.com> (raw)
In-Reply-To: <20060426130518.40F58353DAC@atlas.denx.de>
Wolfgang Denk wrote:
> In message <444F684A.8060406@imagemap.com> you wrote:
>
>> I am new to this but it seems that once we successfully write the
>> environment and protect it, how does (should) one go about writing that
>> same environment to the redundant sector? Is it done with saveenv if
>> the redundant environment is enabled? I guess I need to go look at the
>>
>
> Correct. All you need to do is call "saveenv" twice. [That's why I
> can't see a real need for changing the code.]
>
> Best regards,
>
> Wolfgang Denk
>
Just my uninformed opinion...It seems to me that calling saveenv twice
is misleading. What I mean is that I assume that I have a "golden" copy
of my environment in the redundant area. I should be able to call
saveenv as many times as I wish without touching the contents of the
"golden" copy and that there should be another mechanism to update the
"golden" copy. I had no idea that calling saveenv twice will overwrite
the redundant area, but then again, I am in new to this.
-Randy Smith
next prev parent reply other threads:[~2006-04-26 13:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 19:46 [U-Boot-Users] Redundant environment expected behavior vs current Tolunay Orkun
2006-04-25 21:46 ` Wolfgang Denk
2006-04-25 23:33 ` Tolunay Orkun
2006-04-25 23:55 ` Wolfgang Denk
2006-04-26 0:59 ` Tolunay Orkun
2006-04-26 7:53 ` Wolfgang Denk
2006-04-26 12:32 ` Randy Smith
2006-04-26 13:05 ` Wolfgang Denk
2006-04-26 13:25 ` Randy Smith [this message]
2006-04-26 15:05 ` Wolfgang Denk
2006-04-26 15:29 ` Tolunay Orkun
2006-04-26 16:12 ` Wolfgang Denk
2006-04-26 20:26 ` Stefan Roese
2006-04-27 18:45 ` Jerry Van Baren
2006-04-26 10:05 ` 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=444F74B1.8060909@imagemap.com \
--to=rsmith@imagemap.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.