From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Jim Quinlan <jim2101024@gmail.com>,
Kevin Cernekee <cernekee@gmail.com>,
linux-mtd@lists.infradead.org,
Matthieu CASTET <matthieu.castet@parrot.com>
Subject: Re: [PATCH] mtd: nand: write bad block marker even with BBT
Date: Mon, 12 Dec 2011 22:49:48 +0200 [thread overview]
Message-ID: <1323723000.2297.4.camel@koala> (raw)
In-Reply-To: <1323292100-19280-1-git-send-email-computersforpeace@gmail.com>
On Wed, 2011-12-07 at 13:08 -0800, Brian Norris wrote:
> Add and option (NAND_BBT_WRITE_BBM) for writing bad block markers to
> proper OOB area on each block in addition to flash-based BBT. This is
> useful when:
>
> * bootloader cannot read the flash-based BBT format
> * BBT is corrupted and the flash must be rescanned for bad
> blocks; we want to remember bad blocks that were marked from Linux
>
> Adapted from code by Matthieu CASTET.
>
> Cc: Matthieu CASTET <matthieu.castet@parrot.com>
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
2 questions, perhaps silly, but still:
1. Why wouldn't you make this the only and the default behavior? Why
adding more options instead?
2. Would the case of inconsistency between BBT and OOB markers be
possible to fix-up after the power cut?
Artem.
next prev parent reply other threads:[~2011-12-12 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 21:08 [PATCH] mtd: nand: write bad block marker even with BBT Brian Norris
2011-12-12 20:49 ` Artem Bityutskiy [this message]
2011-12-12 21:53 ` Brian Norris
2011-12-13 7:48 ` Shmulik Ladkani
2011-12-14 20:46 ` Brian Norris
2011-12-17 15:06 ` Artem Bityutskiy
2011-12-19 18:51 ` Brian Norris
2011-12-17 14:54 ` Artem Bityutskiy
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=1323723000.2297.4.camel@koala \
--to=dedekind1@gmail.com \
--cc=cernekee@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=jim2101024@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.com \
/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