From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: kirkwood: Fix chip-delay for GoFlex Net
Date: Mon, 18 Mar 2013 15:33:35 -0400 [thread overview]
Message-ID: <20130318193335.GK13280@titan.lakedaemon.net> (raw)
In-Reply-To: <51476198.2080100@gmail.com>
On Mon, Mar 18, 2013 at 07:48:56PM +0100, Eric Hutter wrote:
> Hi,
>
> This fixes "Too few good blocks within range" issues on GoFlex Net
> by setting chip-delay to 40. I've been using this patch on my device
> for quite a while now (accessing uboot vars is not possible without it).
> The basic problem was discussed at
> http://forum.doozan.com/read.php?2,7451 and I think this fix
> should go mainstream.
>
> Greetings
>
> Eric Hutter
>
>
> Signed-off-by: Eric Hutter <hutter.eric@gmail.com>
> ---
> arch/arm/boot/dts/kirkwood-goflexnet.dts | 1 +
> 1 file changed, 1 insertion(+)
Nice catch! I'll include this in the next round of fixes I push.
thx,
Jason.
next prev parent reply other threads:[~2013-03-18 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 18:48 [PATCH 1/1] ARM: kirkwood: Fix chip-delay for GoFlex Net Eric Hutter
2013-03-18 19:26 ` Andrew Lunn
2013-03-18 21:05 ` Jason Gunthorpe
2013-03-18 19:33 ` Jason Cooper [this message]
2013-03-28 16:36 ` Jason Cooper
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=20130318193335.GK13280@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