From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: linuxppc-dev@ozlabs.org, Feng Kan <fkan@amcc.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/1] Fix ECC Correction bug for SMC ordering for NDFC driver.
Date: Fri, 21 Aug 2009 10:02:15 +0200 [thread overview]
Message-ID: <200908211002.15178.sr@denx.de> (raw)
In-Reply-To: <1250813957-1786-1-git-send-email-fkan@amcc.com>
On Friday 21 August 2009 02:19:17 Feng Kan wrote:
> Fix ECC Correction bug where the byte offset location were double
> fliped causing correction routine to toggle the wrong byte location
> in the ECC segment. The ndfc_calculate_ecc routine change the order
> of getting the ECC code.
> /* The NDFC uses Smart Media (SMC) bytes order */
> ecc_code[0] = p[2];
> ecc_code[1] = p[1];
> ecc_code[2] = p[3];
> But in the Correction algorithm when calculating the byte offset
> location, the b1 is used as the upper part of the address. Which
> again reverse the order making the final byte offset address
> location incorrect.
> byte_addr = (addressbits[b1] << 4) + addressbits[b0];
> The order is change to read it in straight and let the correction
> function to revert it to SMC order.
>
> Signed-off-by: Feng Kan <fkan@amcc.com>
> Acked-by: Victor Gallardo <vgallardo@amcc.com>
> Acked-by: Prodyut Hazarika <phazarika@amcc.com>
Acked-by: Stefan Roese <sr@denx.de>
Would be great if we could get this fix into 2.6.31.
Cheers,
Stefan
next prev parent reply other threads:[~2009-08-21 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 0:19 [PATCH 1/1] Fix ECC Correction bug for SMC ordering for NDFC driver Feng Kan
2009-08-21 0:27 ` Sean MacLennan
2009-08-21 8:02 ` Stefan Roese [this message]
2009-08-21 18:55 ` Sean MacLennan
2009-08-21 18:56 ` Feng Kan
2009-08-21 20:35 ` Victor Gallardo
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=200908211002.15178.sr@denx.de \
--to=sr@denx.de \
--cc=dwmw2@infradead.org \
--cc=fkan@amcc.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxppc-dev@ozlabs.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).