All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Dunn <mikedunn@newsguy.com>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org,
	Shmulik Ladkani <shmulik.ladkani@gmail.com>
Subject: Re: Regarding latest EUCLEAN/bitflip_threshold patchset
Date: Mon, 14 May 2012 12:28:18 -0700	[thread overview]
Message-ID: <4FB15CD2.3040202@newsguy.com> (raw)
In-Reply-To: <4FAEADF1.50308@newsguy.com>

Hi Shmulik, still no joy.  Pasting from the archives again...


> No idea why this happens, others seem to get my posts...


Clearly.  Otherwise you'd be talking to yourself a lot :)


> I see.
> So the current bitflip_threshold scheme is probably not applicable to
> 'nand_do_read_oob' - because the strength over the OOB would probably
> differ from the page's ECC strength.


Correct.  So if for example the diskonchip docg4 implements hamming in oob, and
there are two bitflips, that's uncorrectible.  But two bitflips would not be
considered indicative of a block going bad for a full page read.


> Well, I was also surprised to see that 'nand_do_read_oob' may return
> EUCLEAN or EBADMSG at all.


Yeah, I chose to just gloss over that.


> Digging further, I found out it was a relatively recent addition:
> [041e4575 mtd: nand: handle ECC errors in OOB] by Brian Norris.


Hmmm...

Thanks,
Mike

      parent reply	other threads:[~2012-05-14 19:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 10:26 Regarding latest EUCLEAN/bitflip_threshold patchset Shmulik Ladkani
2012-05-11 11:51 ` Artem Bityutskiy
2012-05-12 18:37   ` Mike Dunn
2012-05-12 20:13     ` Shmulik Ladkani
2012-05-16  6:49       ` Brian Norris
2012-05-16 18:09         ` Mike Dunn
2012-05-17  9:22           ` Shmulik Ladkani
2012-05-14 19:28     ` Mike Dunn [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=4FB15CD2.3040202@newsguy.com \
    --to=mikedunn@newsguy.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=shmulik.ladkani@gmail.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 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.