From: Christopher Harvey <charvey@matrox.com>
To: linux-mtd@lists.infradead.org
Subject: state of support for "external ECC hardware"
Date: Mon, 29 Oct 2012 16:42:27 -0400 [thread overview]
Message-ID: <20121029204227.GA32300@harvey-pc.matrox.com> (raw)
I know of at least one Micron NAND chip that has the ability to handle
ECC completely on the NAND chip itself. All the host has to do is send
data and the OOB section is updated automatically. The automatic ECC
hardware can be enabled and disabled with the "Set Feature" command,
(0xEF) and bit flips are reported via get status after page reads. I
don't see support for this in 2.6.37, and a quick check in the logs
doesn't show anything new for these chips in the latest version of the
kernel. Any idea floating around on this list? Are these chips going
to be the future for NAND and does Linux care about them?
thanks,
Chris
next reply other threads:[~2012-10-29 20:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 20:42 Christopher Harvey [this message]
2012-11-08 11:02 ` state of support for "external ECC hardware" Gerlando Falauto
2012-11-08 15:21 ` Christopher Harvey
2012-11-08 16:32 ` Gerlando Falauto
2012-11-08 16:37 ` Gerlando Falauto
2012-11-08 17:03 ` Christopher Harvey
2012-11-08 17:02 ` Christopher Harvey
2012-11-08 19:07 ` Ivan Djelic
2012-11-09 8:46 ` Ricard Wanderlof
2012-11-12 17:19 ` Gerlando Falauto
2012-11-12 17:35 ` Ivan Djelic
2012-11-12 17:39 ` Gerlando Falauto
2012-11-12 18:52 ` Ivan Djelic
2012-11-14 10:12 ` Gerlando Falauto
2012-11-14 13:24 ` Angus CLARK
2012-11-14 14:48 ` Matthieu CASTET
2012-11-14 20:22 ` Ivan Djelic
2012-11-20 11:13 ` Calvin Johnson
2012-11-20 11:35 ` Gerlando Falauto
2012-11-20 12:12 ` Calvin Johnson
2012-11-20 16:16 ` Ricard Wanderlof
2012-11-08 18:59 ` Ivan Djelic
2012-11-08 19:22 ` Christopher Harvey
2012-11-08 19:33 ` Ivan Djelic
2012-11-08 18:04 ` Ivan Djelic
2012-11-14 10:59 ` Angus CLARK
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=20121029204227.GA32300@harvey-pc.matrox.com \
--to=charvey@matrox.com \
--cc=linux-mtd@lists.infradead.org \
/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).