From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 2/4] mtd/NAND: Add FSMC driver support
Date: Wed, 16 May 2012 11:02:24 -0500 [thread overview]
Message-ID: <4FB3CF90.1000202@freescale.com> (raw)
In-Reply-To: <4FB38454.3080803@st.com>
On 05/16/2012 05:41 AM, Amit Virdi wrote:
> Hi Scott,
>
> On 5/16/2012 2:44 AM, Scott Wood wrote:
>> On 05/07/2012 02:26 AM, Amit Virdi wrote:
>>> + while (num_err--) {
>>> + change_bit(0,&err_idx[i]);
>>> + change_bit(1,&err_idx[i]);
>>> +
>>> + if (err_idx[i]< 512 * 8) {
>>> + change_bit(err_idx[i], dat);
>>> + i++;
>>> + }
>>> + }
>>
>> Is it normal to not count bit flips in the ECC itself?
>>
>
> Correcting bit flip in ECC isn't of any use, so we skipped it.
I think it is useful to report that the bit flip happened, so that the
upper layers know when to scrub the page.
> Otherwise also, the ECC and the data area are not contiguous here as
> they are at different parts of RAM so we couldn't have done
> if (err_idx[i]< (512+13) * 8) {
> here.
You could still increment the error count.
-Scott
next prev parent reply other threads:[~2012-05-16 16:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 7:26 [U-Boot] [PATCH V2 0/4] mtd/NAND: Support for FSMC controller Amit Virdi
2012-05-07 7:26 ` [U-Boot] [PATCH V2 1/4] ARM: Define change_bit routine Amit Virdi
2012-05-07 7:26 ` [U-Boot] [PATCH V2 2/4] mtd/NAND: Add FSMC driver support Amit Virdi
2012-05-15 21:14 ` Scott Wood
2012-05-16 10:41 ` Amit Virdi
2012-05-16 11:05 ` Amit Virdi
2012-05-16 11:31 ` Amit Virdi
2012-05-16 16:02 ` Scott Wood [this message]
2012-05-17 11:21 ` Amit Virdi
2012-05-07 7:26 ` [U-Boot] [PATCH V2 3/4] SPEAr: Configure FSMC driver for NAND interface Amit Virdi
2012-05-07 7:26 ` [U-Boot] [PATCH V2 4/4] mtd/NAND: Remove obsolete SPEAr specific NAND drivers Amit Virdi
2012-05-07 8:19 ` [U-Boot] [PATCH V2 0/4] mtd/NAND: Support for FSMC controller Stefan Roese
2012-05-14 13:49 ` Stefan Roese
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=4FB3CF90.1000202@freescale.com \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/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.