From: ijc@hellion.org.uk (Ian Campbell)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Kirkwood: Add support for Excito Bubba B3
Date: Thu, 02 Jan 2014 22:36:32 +0000 [thread overview]
Message-ID: <1388702192.16958.54.camel@hastur.hellion.org.uk> (raw)
In-Reply-To: <20140102194924.GA3321@obsidianresearch.com>
On Thu, 2014-01-02 at 12:49 -0700, Jason Gunthorpe wrote:
> On Sat, Dec 28, 2013 at 12:01:14PM -0500, Jason Cooper wrote:
>
> > > + * Note: This requires a new'ish version of u-boot, which disables the
> > > + * L2 cache. If your B3 silently fails to boot, u-boot is probably too
> > > + * old. Either upgrade, or consider the following email:
> > > + *
> > > + * http://lists.debian.org/debian-arm/2012/08/msg00128.html
> >
> > Nice, thanks for adding this.
>
> Nifty.. But what is the root cause for the above?
>
> I'm guessing that at some point the the L1 icache has been enabled,
> the L1 dcache disabled, and the L2 cache enabled?
>
> If the pv_fixup runs with both L1 caches off and an empty L2 then it
> shouldn't cause a problem.
I'm not 100% sure but I think the issue is that the kernel expects to be
running with all of the caches off, but u-boot incorrectly left the l2
on. The L2 is probably not empty (because u-boot was using it).
There is some code modifications done at startup (relating to setting
paddr offset?) and since the kernel expects caches to be off it doesn't
do any cache maintenance. Which means that things don't work as
expected, because stuff is cached in L2 dcache and therefore not seen in
the instruction stream (Either icached or uncached).
Anyway, regardless of the specifics running with caches on when the
kernel thinks they are off is going to cause all sorts of oddness...
Ian.
next prev parent reply other threads:[~2014-01-02 22:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 16:12 [PATCH] ARM: Kirkwood: Add support for Excito Bubba B3 Andrew Lunn
2013-12-28 17:01 ` Jason Cooper
2013-12-28 20:59 ` Andrew Lunn
2013-12-28 21:25 ` Jason Cooper
2014-01-02 19:49 ` Jason Gunthorpe
2014-01-02 22:36 ` Ian Campbell [this message]
2014-01-02 23:08 ` Jason Gunthorpe
2014-01-03 0:44 ` Andrew Lunn
2014-01-10 19:20 ` Jason Cooper
2014-01-10 19:44 ` Jason Gunthorpe
2014-01-10 19:54 ` Jason Cooper
2014-01-10 23:02 ` Andrew Lunn
2014-01-11 0:19 ` Jason Gunthorpe
2014-01-11 15:59 ` Russell King - ARM Linux
2014-01-13 14:44 ` 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=1388702192.16958.54.camel@hastur.hellion.org.uk \
--to=ijc@hellion.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).