public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH reword] ARM: MVEBU: Netgear RN102: Use Hardware BCH ECC
Date: Sun, 14 Sep 2014 00:18:47 -0400	[thread overview]
Message-ID: <20140914041847.GB21986@titan.lakedaemon.net> (raw)
In-Reply-To: <54150349.7050503@killerwolves.net>

On Sun, Sep 14, 2014 at 12:54:01PM +1000, Ben Peddell wrote:
> On 14/09/14 07:08, Jason Cooper wrote:
> > On Wed, Sep 10, 2014 at 06:55:41PM +1000, klightspeed at killerwolves.net wrote:
> >> The bootloader on the Netgear ReadyNAS RN102 uses Hardware BCH ECC
> >> (strength = 4), while the pxa3xx NAND driver by default uses 
> >> Hamming ECC (strength = 1).
> >>
> >> This patch changes the ECC mode on these machines to match that
> >> of the bootloader and of the stock firmware. That way, it is
> >> now possible to update the kernel from userland (e.g. using
> >> standard tools from mtd-utils package); u-boot will happily
> >> load and boot it.
> >>
> >> Fixes: 92beaccd8b49 ("ARM: mvebu: Enable NAND controller in ReadyNAS 102 .dts file")
> >> Signed-off-by: Ben Peddell <klightspeed@killerwolves.net>
> >> Acked-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> >> Tested-by: Arnaud Ebalard <arno@natisbad.org>
> >> ---
> >>  arch/arm/boot/dts/armada-370-netgear-rn102.dts | 4 ++++
> >>  1 file changed, 4 insertions(+)
> > 
> > I've already applied this the mvebu/fixes:
> > 
> >   500abb6ccb9e ARM: mvebu: Netgear RN2120: Use Hardware BCH ECC
> 
> That patch only affects arch/arm/boot/dts/armada-xp-netgear-rn2120.dts
> 
> The patch I posted affects arch/arm/boot/dts/armada-370-netgear-rn102.dts

Gah!  You're right.  Applied to mvebu/fixes and Cc'd the stable v3.14+

thx,

Jason.

      reply	other threads:[~2014-09-14  4:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10  8:55 [PATCH reword] ARM: MVEBU: Netgear RN102: Use Hardware BCH ECC klightspeed at killerwolves.net
2014-09-13 21:08 ` Jason Cooper
2014-09-14  2:54   ` Ben Peddell
2014-09-14  4:18     ` Jason Cooper [this message]

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=20140914041847.GB21986@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=linux-arm-kernel@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