From: Brian Foster <brian.foster@maximintegrated.com>
To: <linux-mtd@lists.infradead.org>
Subject: [Q] Using Micron 4-bit on-die ECC with v2.6.36 kernel?
Date: Wed, 19 Jun 2013 16:14:53 +0200 [thread overview]
Message-ID: <17588192.75Agdljyqk@laclwks004> (raw)
Our current reference Linux kernel for the MAX32590 (JIBE)
is based on v2.6.36. (Unfortunately, upgrading to a more
recent version is not within the timeframe for solving the
current problem.) Our recent reference boards use one of
those Micron NAND chips with an on-die 4-bit ECC, which we
have basically ignored: To-date, we have simply used the
usual 1-bit ECC (i.e., living dangerously!).
This must change, and indeed we now have a case on my desk
where, had we been using the on-die ECC, it would have saved
us a ton of grief. The problem is our kernel version is far
too old to take advantage of any of the recent-ish work for
on-die ECC.
Hence, I am looking into the possibility of adding on-die ECC
support to our JIBE controller driver specifically for such
NAND chips (or at least the specific Micron NAND chip on the
reference boards). Broadly, pretending JIBE's H/W directly
supports on-die ECC, but actually doing the work in the driver.
A similar trick we played in the past (bitwise-inverted ECC
(now obsoleted and long-removed from the driver)) suggests
this is not too difficult.
I am looking for hints (suggestions), gotchas (warnings),
and/or any examples of similar (or other plausible) approaches.
Or for something I am overlooking in (or available for) kernels
of approximately the vintage we are using.
Thanks & cheers!
-blf-
p.s. At the present time, I am not too interested in the
problem of converting existing boards. This MAY change
as the scope and details of the solution become more
apparent.
--
Brian Foster
Principal MTS, Software | La Ciotat, France
Maxim Integrated | http://www.maximintegrated.com/
next reply other threads:[~2013-06-19 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 14:14 Brian Foster [this message]
2013-06-19 21:40 ` [Q] Using Micron 4-bit on-die ECC with v2.6.36 kernel? David Mosberger-Tang
2013-07-03 8:49 ` Brian Foster
[not found] ` <CACwUX0NXgTC=uQ7CZoY=anBuMhfyN31GFuYAV5EhBUZT9Nm2_w@mail.gmail.com>
2013-07-04 12:05 ` [PATCH] Init ONFI get/set features in a more logical place Brian Foster
2013-08-05 9:39 ` Artem Bityutskiy
2013-07-04 12:35 ` [Q] Using Micron 4-bit on-die ECC with v2.6.36 kernel? Brian Foster
[not found] ` <CACwUX0PaXg+hAqjeB2AK+7FEzr506RTNfNSHQAW+BJ-AnAQxKA@mail.gmail.com>
2013-07-04 13:07 ` Brian Foster
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=17588192.75Agdljyqk@laclwks004 \
--to=brian.foster@maximintegrated.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