From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Redundant environment expected behavior vs current
Date: Wed, 26 Apr 2006 10:29:20 -0500 [thread overview]
Message-ID: <444F91D0.9080904@orkun.us> (raw)
In-Reply-To: <20060426150545.C82D6353DAC@atlas.denx.de>
I will drop in this post to put some final remarks...
Wolfgang Denk wrote:
> In message <444F74B1.8060909@imagemap.com> you wrote:
>> 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
>
> No. That "golden" copy is what we call "default environment" - you
> get this when you lose your environment (with redundand environment
> it means that you lose both copies).
Yet, the default environment normally does not contain such important
stuff like ethaddr which is assigned per board.
>
>> 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
>
> That's not how redundance is defined. You are looking for a backup
> copy, which is provided by the default environment.
Indeed redundancy of environment in U-Boot is rather different than I am
accustomed to.
Anyway, at least I understand how this stuff works much better now and I
hope this discussion will probably help other developers understand that
what they might be getting with redundant environment right now might
not be exactly what they think they are getting.
I really hoped you would allow to introduce the choice of functionality.
It would break no existing boards. I have to think about maintaining an
out-of-three patch for this case :(
Best regards,
Tolunay
next prev parent reply other threads:[~2006-04-26 15:29 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
2006-04-26 15:05 ` Wolfgang Denk
2006-04-26 15:29 ` Tolunay Orkun [this message]
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=444F91D0.9080904@orkun.us \
--to=listmember@orkun.us \
--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.