All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Williams <Aaron.Williams@caviumnetworks.com>
To: <linux-kernel@vger.kernel.org>
Cc: Ivan Djelic <ivan.djelic@parrot.com>
Subject: MTD NAND BCH support for 24 bits/1K of ECC correction?
Date: Thu, 28 Mar 2013 15:23:01 -0700	[thread overview]
Message-ID: <5154C2C5.5000903@caviumnetworks.com> (raw)

Hi all,

I am trying to clean up our OCTEON NAND flash driver in the Linux kernel 
and enable support for multi-bit ECC using BCH and am having some 
issues. I am able to successfully work with NAND flash that requires 4 
bits ECC per 512 bytes but I am having issues with one of our boards 
that has a NAND device that requires 24 bits of ECC per 1024 bytes.

I was wondering if ECC of this magnitude has been successfully tested in 
the past. By my calculations I should have 42 bytes of ECC per 1K block 
(m=14, t=24 for 336 bits of ECC data). My problem is that when decoding 
an encoded block I am seeing that nroots != err in decode_bch() after 
find_poly_roots(). I am seeing this for all of the blocks I attempt to 
read. As far as I can tell the data being sent to BCH is good, though it 
might have a few bad bits but nowhere near 24.

I am also seeing this same behavior in my U-Boot code which uses the 
identical bch and nand_bch code.

Cheers,

Aaron Williams

-- 
Aaron Williams
Software Engineer
Cavium, Inc.
(408) 943-7198  (510) 789-8988 (cell)



             reply	other threads:[~2013-03-28 22:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28 22:23 Aaron Williams [this message]
2013-03-29  9:02 ` MTD NAND BCH support for 24 bits/1K of ECC correction? Ivan Djelic
2013-03-29  9:02   ` Ivan Djelic
2013-03-30  5:40   ` Aaron Williams
2013-03-30  5:40     ` Aaron Williams

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=5154C2C5.5000903@caviumnetworks.com \
    --to=aaron.williams@caviumnetworks.com \
    --cc=ivan.djelic@parrot.com \
    --cc=linux-kernel@vger.kernel.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 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.