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 08:32:10 -0400 [thread overview]
Message-ID: <444F684A.8060406@imagemap.com> (raw)
In-Reply-To: <20060426075331.C04C8353AC4@atlas.denx.de>
Wolfgang Denk wrote:
> In message <444EC5F1.10205@orkun.us> you wrote:
>
>> time U-Boot will switch to the second copy but second copy does not have
>> the latest stuff we put/modified because we did not sync them.
>>
>
> If theis is your concern, then sync it. Nothing prevents you from
> doing this.
>
>
>>>> environment after one copy is written might not save us in certain
>>>> situations.
>>>>
>>> Which are?
>>>
>>>
>> Say, I am booting one of the two kernels/initrd in flash. Or NFS booting
>> from a different IP etc. Supplying a different kernel command line.
>>
>
> How would this corrupt an already stored and write protected
> environment sector?
>
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
code.
-Randy Smith
next prev parent reply other threads:[~2006-04-26 12:32 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 [this message]
2006-04-26 13:05 ` Wolfgang Denk
2006-04-26 13:25 ` Randy Smith
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=444F684A.8060406@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox