From: Ivan Djelic <ivan.djelic@parrot.com>
To: "Philip, Avinash" <avinashphilip@ti.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: mtd oob test is failing consistently at same places in NAND flash
Date: Tue, 8 May 2012 20:45:16 +0200 [thread overview]
Message-ID: <20120508184516.GA16380@parrot.com> (raw)
In-Reply-To: <518397C60809E147AF5323E0420B992E3E934DD0@DBDE01.ent.ti.com>
On Tue, May 08, 2012 at 04:09:46PM +0100, Philip, Avinash wrote:
> On Tue, May 08, 2012 at 18:53:54, Ivan Djelic wrote:
> > On Tue, May 08, 2012 at 01:33:06PM +0100, Philip, Avinash wrote:
> > > Hi,
> > >
> > > We are having an 8-bit NAND part (MT29F2G08ABAEAWP from Micron)
> > > connected to GPMC Module (General purpose memory controller) from TI.
> >
> > Hi,
> > How is ecc performed ?
> > Using NAND internal ecc ? or with GPMC 1-bit Hamming ? 4-bit/8-bit BCH ?
> > Which version of omap2 driver are you using ?
> > Is OOB also ECC-protected ?
>
> Hardware ECC is performing.
> 4-bit BCH ECC scheme is used.
> I am using omap2 driver in Linux 3.2.0 Kernel. Don't know omap2 driver version.
You are probably using a patched kernel, since 3.2.0 does not have GPMC BCH support ?!
What is your ecc layout ? Does it expose oobfree regions ?
> No, OOB is not ECC protected.
Well, in that case, isn't it normal that mtd_oobtest should fail if there happens to be
a single bitflip in the available OOB area ? (of size mtd->ecclayout->oobavail for each page)
BR,
--
Ivan
next prev parent reply other threads:[~2012-05-08 18:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 12:33 mtd oob test is failing consistently at same places in NAND flash Philip, Avinash
2012-05-08 13:23 ` Ivan Djelic
2012-05-08 15:09 ` Philip, Avinash
2012-05-08 15:23 ` Philip, Avinash
2012-05-08 18:45 ` Ivan Djelic [this message]
2012-05-09 15:12 ` Philip, Avinash
2012-05-09 15:24 ` Ivan Djelic
2012-05-09 15:46 ` Philip, Avinash
2012-05-09 16:05 ` Ivan Djelic
2012-05-10 7:51 ` Ricard Wanderlof
2012-05-09 6:37 ` Ricard Wanderlof
2012-05-10 13:01 ` Artem Bityutskiy
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=20120508184516.GA16380@parrot.com \
--to=ivan.djelic@parrot.com \
--cc=avinashphilip@ti.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;
as well as URLs for NNTP newsgroup(s).