All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Barada <peter.barada@logicpd.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Question regarding NAND environment
Date: Thu, 26 Jan 2012 12:05:56 -0500	[thread overview]
Message-ID: <4F2187F4.1000503@logicpd.com> (raw)

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.

Can/does the code save multiple copies of the environment across the
three blocks, 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.  In my case the environment is 32K and
each block is 128K, so I should be able to write six copies into NAND
(if all three blocks are good), and if one block then goes bad I can
still erase one of the other blocks (while the other remaining good
block holds at least one valid copy of the environment).

If u-boot doesn't do this currently is there any interest in a patch for
such?

-- 
Peter Barada
peter.barada at logicpd.com

             reply	other threads:[~2012-01-26 17:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 17:05 Peter Barada [this message]
2012-01-26 17:27 ` [U-Boot] Question regarding NAND environment Scott Wood
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=4F2187F4.1000503@logicpd.com \
    --to=peter.barada@logicpd.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.