From: Scott Wood <scottwood@freescale.com>
To: Richard Weinberger <richard@nod.at>
Cc: "Martin Strbačka" <martin.strbacka@nic.cz>,
"Tomas Hlavacek" <tomas.hlavacek@nic.cz>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Missing support for ECC_SOFT_BCH in fsl-elbc-nand
Date: Thu, 9 Apr 2015 21:25:24 -0500 [thread overview]
Message-ID: <1428632724.22867.571.camel@freescale.com> (raw)
In-Reply-To: <55195BA8.2080102@nod.at>
On Mon, 2015-03-30 at 16:20 +0200, Richard Weinberger wrote:
> Hi!
>
> Am 30.03.2015 um 10:35 schrieb Martin Strbačka:
> > On 27.3.2015 17:02, Richard Weinberger wrote:
> >> On Fri, Mar 27, 2015 at 3:13 PM, Martin Strbačka <martin.strbacka@nic.cz> wrote:
> >>> Hello,
> >>>
> >>> in our product we have Freescale P2020 SoC together with Micron
> >>> MT29F2G08ABAEAWP NAND. Lately we discovered that the internal driver
> >>> (fsl-elbc-nand) supports only 1-bit HW ECC. So we would like to switch
> >>> to ECC_SOFT_BCH (or on-die ECC as I saw some patches in this list
> >>> recently). Do you know if anybody works on this or are there any patches
> >>> already?
> >>
> >> Works on what?
> >> I work (obviously) on on-die ECC support.
> >
> > I mean working on support ECC_SOFT_BCH or on-die ECC in fsl-elbc-nand. I
> > believe that fsl-elbc-nand needs some modifications to support those ECC
> > modes. Or am I wrong?
>
> Ah. My on-die ECC patches should work with any NFC. If you look
> at the diffstat you'll notice that it does not touch any NAND driver.
> Unless fsl-elbc-nand doesn't do strange things it should just work.
> Please give it a try, feedback is very welcome! :)
eLBC does "strange things" as its programming model is higher-level than
what nand_base.c was designed for.
-Scott
next prev parent reply other threads:[~2015-04-10 2:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 14:13 Missing support for ECC_SOFT_BCH in fsl-elbc-nand Martin Strbačka
2015-03-27 16:02 ` Richard Weinberger
2015-03-30 8:35 ` Martin Strbačka
2015-03-30 14:20 ` Richard Weinberger
2015-04-10 2:25 ` Scott Wood [this message]
2015-04-12 22:30 ` Tomas Hlavacek
2015-04-13 19:12 ` Scott Wood
2015-04-13 21:56 ` Tomas Hlavacek
2015-04-14 0:58 ` Scott Wood
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=1428632724.22867.571.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=linux-mtd@lists.infradead.org \
--cc=martin.strbacka@nic.cz \
--cc=richard@nod.at \
--cc=tomas.hlavacek@nic.cz \
/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).