From: Daniel Palmer <daniel@0x0f.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: linux-mtd@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mtd: spinand: add support for Foresee FS35ND01G-S1Y2
Date: Tue, 23 Mar 2021 20:47:10 +0900 [thread overview]
Message-ID: <CAFr9PX=KMZuzp61Hq=2WdHyEzE=6J7HEPWZxPs7FEqiH-G8wFw@mail.gmail.com> (raw)
In-Reply-To: <20210323113233.3523d66b@xps13>
Hi Miquel,
On Tue, 23 Mar 2021 at 19:32, Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> You can run nandbiterrs -i /dev/mtdX
>
> You'll see if there is ECC correction or not (and its level).
These are results I get for both of the nandbiterrs tests.
# nandbiterrs -i /dev/mtd1
incremental biterrors test
Successfully corrected 0 bit errors per subpage
Inserted biterror @ 0/5
Read reported 4 corrected bit errors
ECC failure, invalid data despite read success
# nandbiterrs -o /dev/mtd1
overwrite biterrors test
Read reported 4 corrected bit errors
Failed to recover 1 bitflips
Bit error histogram (883 operations total):
Page reads with 0 corrected bit errors: 845
Page reads with 1 corrected bit errors: 0
Page reads with 2 corrected bit errors: 0
Page reads with 3 corrected bit errors: 0
I guess this means ECC is there and it's working.
Thanks,
Daniel
next prev parent reply other threads:[~2021-03-23 11:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 9:57 [PATCH v2] mtd: spinand: add support for Foresee FS35ND01G-S1Y2 Daniel Palmer
2021-02-15 10:24 ` Miquel Raynal
2021-02-15 10:53 ` Daniel Palmer
2021-02-15 11:16 ` Miquel Raynal
2021-02-15 11:34 ` Daniel Palmer
2021-03-22 12:44 ` Daniel Palmer
2021-03-22 18:32 ` Miquel Raynal
2021-03-23 9:33 ` Daniel Palmer
2021-03-23 10:32 ` Miquel Raynal
2021-03-23 11:47 ` Daniel Palmer [this message]
2021-03-23 14:06 ` Miquel Raynal
2021-03-23 14:14 ` Daniel Palmer
2021-03-26 14:09 ` Daniel Palmer
2021-04-07 8:02 ` Miquel Raynal
2021-04-07 12:01 ` Daniel Palmer
2021-04-08 15:49 ` Miquel Raynal
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='CAFr9PX=KMZuzp61Hq=2WdHyEzE=6J7HEPWZxPs7FEqiH-G8wFw@mail.gmail.com' \
--to=daniel@0x0f.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.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;
as well as URLs for NNTP newsgroup(s).