mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Boaz Ben-David <boaz.bd@wellsense-tech.com>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: protecting env partitions from bad blocks
Date: Sun, 5 Jun 2011 14:50:01 +0300	[thread overview]
Message-ID: <4DEB6D69.5030003@wellsense-tech.com> (raw)

Hi all,

I want to protect the env partition on my device from bad blocks 
(created during operation or already there out of the factory).
Couldn't find any good documentation regarding this issue, so I have 
some questions:

1. Exactly what capabilities the bb devices in Barebox give me?
2. I was thinking of somehow assigning the env partition larger than 
required in order to later
handle bad blocks by moving the block currenly being used to be the 
first good block.
Is this a good approach or maybe there is something already ready and I 
shouldn't bother because I am totally missing the point?

Thanks,

Boaz.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2011-06-05 11:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-05 11:50 Boaz Ben-David [this message]
2011-06-05 12:11 ` Juergen Beisert
2011-06-05 12:38   ` Boaz Ben-David
2011-06-06  7:25     ` Sascha Hauer

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=4DEB6D69.5030003@wellsense-tech.com \
    --to=boaz.bd@wellsense-tech.com \
    --cc=barebox@lists.infradead.org \
    /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