From: Marc Reilly <marc@cpdesign.com.au>
To: barebox@lists.infradead.org
Cc: Wolfram Sang <w.sang@pengutronix.de>
Subject: Re: [PATCH 0/2] allow scrubbing (erasing of bad blocks)
Date: Fri, 21 Dec 2012 09:06:04 +1100 [thread overview]
Message-ID: <5677378.zGTgKWBU2t@dev1.cpdesign> (raw)
In-Reply-To: <1355415502-30673-1-git-send-email-w.sang@pengutronix.de>
Hi,
On Thursday, December 13, 2012 05:18:20 PM Wolfram Sang wrote:
> This patch series first adds a flag to mtd devices which disables special
> treatment for bad blocks. That means, they are handled like every other good
> block. The second one then adds a scrub command which is basically a simple
> erase, only that bad blocks are treated like good blocks and are trying to
> be erased (which may succeed or not). This is really *not recommended*,
> except for certain development use cases!
Much nicer than the hacks I did to clear the BBT !
(unfortunately, don't have any boards that I can test on at the moment).
Cheers,
Marc
>
> Wolfram Sang (2):
> mtd: nand: add flag to allow erasing of bad blocks
> commands: add scrub
>
> commands/Kconfig | 8 +++++
> commands/flash.c | 68
> ++++++++++++++++++++++++++++++++++++++++- drivers/mtd/core.c |
> 9 +++++-
> drivers/mtd/nand/nand_write.c | 37 +++++++++++-----------
> include/linux/mtd/mtd-abi.h | 2 ++
> 5 files changed, 105 insertions(+), 19 deletions(-)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-12-20 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 16:18 [PATCH 0/2] allow scrubbing (erasing of bad blocks) Wolfram Sang
2012-12-13 16:18 ` [PATCH 1/2] mtd: nand: add flag to ignore special handling of bad blocks Wolfram Sang
2012-12-13 16:18 ` [PATCH 2/2] commands: add scrub Wolfram Sang
2012-12-20 22:06 ` Marc Reilly [this message]
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=5677378.zGTgKWBU2t@dev1.cpdesign \
--to=marc@cpdesign.com.au \
--cc=barebox@lists.infradead.org \
--cc=w.sang@pengutronix.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.