From: "Martin Strbačka" <martin.strbacka@nic.cz>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: 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: Mon, 30 Mar 2015 10:35:55 +0200 [thread overview]
Message-ID: <55190AEB.8010704@nic.cz> (raw)
In-Reply-To: <CAFLxGvx-nXQQzOmpJyoGw5a6U8iEM_cr61vJx9aRNu5rAbnNLg@mail.gmail.com>
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?
next prev parent reply other threads:[~2015-03-30 8:36 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 [this message]
2015-03-30 14:20 ` Richard Weinberger
2015-04-10 2:25 ` Scott Wood
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=55190AEB.8010704@nic.cz \
--to=martin.strbacka@nic.cz \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
--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 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.