From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mtd: atmel_nand: according to pmecc version to perform 0xff page correction
Date: Mon, 9 Feb 2015 11:04:59 -0600 [thread overview]
Message-ID: <1423501499.4338.1.camel@aoeu.buserror.net> (raw)
In-Reply-To: <54CF1450.2050605@atmel.com>
On Mon, 2015-02-02 at 14:08 +0800, Josh Wu wrote:
> Hi, Scott
>
> On 1/16/2015 4:24 PM, Andreas Bie?mann wrote:
> > Hi Bo, Josh,
> >
> > On 01/16/2015 07:50 AM, Josh Wu wrote:
> >> Hi, Bo
> >>
> >> On 1/16/2015 1:27 PM, Bo Shen wrote:
> >>> Hi Josh,
> >>>
> >>> On 01/16/2015 11:54 AM, Josh Wu wrote:
> >>>> As the PMECC hardware has different version. In SAMA5D4 chip, the
> >>>> PMECC ip
> >>>> can generate 0xff pmecc ECC value for all 0xff sector.
> >>>>
> >>>> According to this, add PMECC version check, if it's SAMA5D4 then we
> >>>> always
> >>>> let PMECC hardware to correct it.
> >>>>
> >>>> Signed-off-by: Josh Wu <josh.wu@atmel.com>
> >>> except the nitpick.
> >>>
> >>> Acked-by: Bo Shen <voice.shen@atmel.com>
> > Acked-by: Andreas Bie?mann <andreas.devel@googlemail.com>
>
> Would you pick this patch into your tree with Bo and Andreas's Acked-by?
> Thanks.
I won't be able to apply anything for at least a week and a half...
I'll look at it then if it hasn't been applied yet, but I'm fine with
the custodian for the relevant hardware taking it in the meantime.
-Scott
next prev parent reply other threads:[~2015-02-09 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 3:54 [U-Boot] [PATCH] mtd: atmel_nand: according to pmecc version to perform 0xff page correction Josh Wu
2015-01-16 5:27 ` Bo Shen
2015-01-16 6:50 ` Josh Wu
2015-01-16 8:24 ` Andreas Bießmann
2015-01-16 8:51 ` Josh Wu
2015-02-02 6:08 ` Josh Wu
2015-02-09 17:04 ` Scott Wood [this message]
2015-02-09 21:51 ` Andreas Bießmann
2015-02-10 1:44 ` Josh Wu
2015-02-07 22:46 ` [U-Boot] " Andreas Bießmann
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=1423501499.4338.1.camel@aoeu.buserror.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox