<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.38">
<TITLE>RE: [PATCH 1/1] Fix ECC Correction bug for SMC ordering for NDFC driver.</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Yes, I have considered that. However, it would make the #define rather confusing<BR>
for the rest.<BR>
<BR>
Cheers,<BR>
Feng<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Sean MacLennan [<A HREF="mailto:smaclennan@pikatech.com">mailto:smaclennan@pikatech.com</A>]<BR>
Sent: Fri 8/21/2009 11:55 AM<BR>
To: Feng Kan<BR>
Cc: linuxppc-dev@ozlabs.org; linux-mtd@lists.infradead.org; Feng Kan<BR>
Subject: Re: [PATCH 1/1] Fix ECC Correction bug for SMC ordering for NDFC driver.<BR>
<BR>
On Thu, 20 Aug 2009 17:19:17 -0700<BR>
Feng Kan <fkan@amcc.com> wrote:<BR>
<BR>
> Fix ECC Correction bug where the byte offset location were double<BR>
> fliped causing correction routine to toggle the wrong byte location<BR>
> in the ECC segment. The ndfc_calculate_ecc routine change the order<BR>
> of getting the ECC code.<BR>
<BR>
It looks like another fix for this bug is to leave the current code<BR>
alone and turn off CONFIG_MTD_NAND_ECC_SMC.<BR>
<BR>
This could be a better fix if this is the way u-boot currently works.<BR>
Has anybody verified if the current u-boot has the ECC problem?<BR>
<BR>
Cheers,<BR>
Sean<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>