From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Raphael Pereira <raphaelpereira@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: Suport for gf_len 14 in gpmi-nand for i.MX23 using Software BCH ECC
Date: Sun, 5 Aug 2018 17:09:49 +0200 [thread overview]
Message-ID: <20180805170949.099b190a@bbrezillon> (raw)
In-Reply-To: <20180804115555.667b3fb8@xps13>
On Sat, 4 Aug 2018 11:55:55 +0200
Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> Hi Raphael,
>
> Raphael Pereira <raphaelpereira@gmail.com> wrote on Wed, 1 Aug 2018
> 18:29:32 -0300:
>
> > Hi,
> >
> > I would like to know if it is possible to use the Software BCH ECC
> > implementation to support a GF14 (ECC size == 1024) 40 bit ECC strengh
> > flash (MT29F32G08CBADA) on a GF13 (ECC size == 512) 20 bit ECC strengh
> > only i.MX23 processor.
>
> I am not sure to understand correctly your request. What do you mean
> by "GF13 only i.MX23 processor"? I suppose you refer to the raw NAND
> controller abilities? If yes, then why do you care if you use soft
> BCH?
>
> And the ECC requirements is just an indication in terms of
> correctability, how is 40 bits per 1024 bytes different than 20 bits
> per 512?
Well, it is different. In 40b/1024B mode you can fix 40 bits no matter
where they are in the the 1k block (even if they all appear to be in
the first 512 bytes). In 20b/512B mode, you can only fix 20 bits on a
512B portion. So 20b/512B is weaker than 40b/1KB.
prev parent reply other threads:[~2018-08-05 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 21:29 Suport for gf_len 14 in gpmi-nand for i.MX23 using Software BCH ECC Raphael Pereira
2018-08-04 9:55 ` Miquel Raynal
2018-08-04 11:22 ` Raphael Pereira
2018-08-04 17:33 ` Miquel Raynal
2018-08-05 0:39 ` Raphael Pereira
2018-08-05 8:57 ` Boris Brezillon
2018-08-05 9:13 ` Boris Brezillon
2018-08-05 15:34 ` Raphael Pereira
2018-08-05 15:09 ` Boris Brezillon [this message]
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=20180805170949.099b190a@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=raphaelpereira@gmail.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).