From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Question regarding NAND environment
Date: Thu, 26 Jan 2012 11:27:35 -0600 [thread overview]
Message-ID: <4F218D07.8060204@freescale.com> (raw)
In-Reply-To: <4F2187F4.1000503@logicpd.com>
On 01/26/2012 11:05 AM, Peter Barada wrote:
> I'm trying to have a robust environment stored in NAND, and three blocks
> of space available to store it in.
>
> Looking at the REDUND code, I see it only keeps two copies of the
> environment regardless of the amount of space available. Instead I'm
> looking to use CONFIG_ENV_RANGE to handle the extra blocks.
CONFIG_ENV_RANGE and CONFIG_ENV_*_REDUND are orthogonal, not alternatives.
> Can/does the code save multiple copies of the environment across the
> three blocks,
No. Its purpose is to provide room to skip blocks that are formally
marked as bad.
If you want REDUND with more than two copies, you'll have to modify the
REDUND code to support that.
> and can readenv read copies of the environment (skipping
> bad blocks) until it finds one good environment? I'm trying to prevent
> any corruption from happening if (unlikely but possible) power fails
> while saving the environment.
Why are two copies insufficient for that?
-Scott
next prev parent reply other threads:[~2012-01-26 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 17:05 [U-Boot] Question regarding NAND environment Peter Barada
2012-01-26 17:27 ` Scott Wood [this message]
2012-01-26 17:34 ` Peter Barada
2012-01-27 21:46 ` Scott Wood
2012-01-27 22:08 ` Peter Barada
2012-01-27 22:25 ` Tom Rini
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=4F218D07.8060204@freescale.com \
--to=scottwood@freescale.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