From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Adrian Hunter <adrian.hunter@nokia.com>
Cc: Artem Bityutskiy <dedekind@infradead.org>,
Darwin Rambo <drambo@broadcom.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS and hardware ECC of all FF pages of MLC NAND
Date: Thu, 24 Sep 2009 17:36:59 +0200 [thread overview]
Message-ID: <4ABB921B.8090500@parrot.com> (raw)
In-Reply-To: <4ABB7224.8000804@nokia.com>
Adrian Hunter a écrit :
> Darwin Rambo wrote:
>
>> 2. for initial downloading, should an ECC be programmed on all FF data pages? Is there any correction advantage?
>
> In your case, as you have discovered, you must not program ECC for FF pages at
> the end of eraseblocks.
>
The tricky part is when you read FF pages with ecc in mtd. You will get
an ecc error.
If the ecc writing is done on software you can always xor the ecc code
to make it "FF for FF data".
But if everything is done by hardware...
Matthieu
next prev parent reply other threads:[~2009-09-24 15:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 21:31 UBIFS and hardware ECC of all FF pages of MLC NAND Darwin Rambo
2009-09-24 13:20 ` Adrian Hunter
2009-09-24 14:51 ` Artem Bityutskiy
2009-09-24 15:36 ` Matthieu CASTET [this message]
2009-09-25 7:05 ` Artem Bityutskiy
2009-09-29 13:26 ` Darwin Rambo
2009-09-29 15:42 ` Artem Bityutskiy
2009-09-29 16:13 ` Darwin Rambo
2009-09-29 16:20 ` Artem Bityutskiy
2009-09-29 17:03 ` Darwin Rambo
2009-10-11 8:39 ` Artem Bityutskiy
2009-10-11 14:38 ` Darwin Rambo
2009-10-11 15:04 ` Artem Bityutskiy
2009-10-11 17:36 ` Darwin Rambo
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=4ABB921B.8090500@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=adrian.hunter@nokia.com \
--cc=dedekind@infradead.org \
--cc=drambo@broadcom.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