All of lore.kernel.org
 help / color / mirror / Atom feed
From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Kirkwood: Add support for Excito Bubba B3
Date: Thu, 2 Jan 2014 12:49:24 -0700	[thread overview]
Message-ID: <20140102194924.GA3321@obsidianresearch.com> (raw)
In-Reply-To: <20131228170114.GH19878@titan.lakedaemon.net>

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.

If it runs with the icache on lines will be pulled into the L2 by
icache fetching and won't be updated by uncached L1 dcache writes.

Is uboot running the kernel with the icache turned on but dcache
turned off?

>From a kernel side, a possible way to address this might be to move
the pv fixup (__fixup_a_pv_table?) after the mmu and caches are
switched on.

But really, any memory writes done prior to enabling the dcache would
risk getting lost...

Jason

  parent reply	other threads:[~2014-01-02 19:49 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 [this message]
2014-01-02 22:36     ` Ian Campbell
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=20140102194924.GA3321@obsidianresearch.com \
    --to=jgunthorpe@obsidianresearch.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.