From: Shmulik Ladkani <shmulik.ladkani@gmail.com>
To: Matthieu CASTET <matthieu.castet@parrot.com>
Cc: Brian Norris <computersforpeace@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [RFC] nand_btt : use nand chip->block_bad
Date: Sat, 30 Jun 2012 23:02:52 +0300 [thread overview]
Message-ID: <20120630230252.58ca6bb4@halley> (raw)
In-Reply-To: <4FED6A2E.9010603@parrot.com>
Hi,
On Fri, 29 Jun 2012 10:41:18 +0200 Matthieu CASTET <matthieu.castet@parrot.com> wrote:
> > - The new scheme lacks the potential error correction offered by the
> > mtd_read_oob call (invoked from the original scan functions).
> > OTOH, currently, AFAIK, it is only offered by an out-of-tree driver.
> Could you explain more here ?
> The current scheme doesn't handle bitflip in bad block. We don't care about
> error correction : bad block are not protected by ecc !
I was refering to utilizing the ECC when reading the OOB, so we won't
get a false "bad" indication when reading the BBM from the OOB.
See this post (and subsequent ones):
http://lists.infradead.org/pipermail/linux-mtd/2012-June/042203.html
Regards,
Shmulik
next prev parent reply other threads:[~2012-06-30 20:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 15:47 [RFC] nand_btt : use nand chip->block_bad Matthieu CASTET
2012-06-28 18:31 ` Shmulik Ladkani
2012-06-29 8:41 ` Matthieu CASTET
2012-06-30 20:02 ` Shmulik Ladkani [this message]
2012-07-02 8:29 ` Matthieu CASTET
2012-07-24 3:53 ` Brian Norris
2012-07-25 11:02 ` Shmulik Ladkani
2012-08-06 22:21 ` Brian Norris
2012-08-07 7:09 ` Shmulik Ladkani
2012-09-18 1:06 ` Brian Norris
2012-09-18 1:28 ` Scott Wood
2012-09-26 22:43 ` Brian Norris
2012-09-26 22:57 ` Scott Wood
2012-09-26 23:15 ` Brian Norris
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=20120630230252.58ca6bb4@halley \
--to=shmulik.ladkani@gmail.com \
--cc=computersforpeace@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