From: michael@walle.cc (Michael Walle)
To: linux-arm-kernel@lists.infradead.org
Subject: arm and patch phys offset
Date: Wed, 14 Dec 2011 00:17:49 +0100 [thread overview]
Message-ID: <201112140017.49567.michael@walle.cc> (raw)
In-Reply-To: <alpine.LFD.2.02.1112122256580.2907@xanadu.home>
Am Dienstag 13 Dezember 2011, 05:01:30 schrieb Nicolas Pitre:
> > Seems like the l2 cache is enabled after uboot starts the linux kernel.
> > I'll dig deeper into that tomorrow.
> >
> > For now, i appended
> >
> > l2_cache_disable();
> >
> > to uboots cleanup_before_linux() and all stubs seems to be patched
> > correctly.
>
> Strange. Having l2 enabled shouldn't cause such trouble.
There is a similar commit in uboots git tree:
http://git.denx.de/?p=u-
boot.git;a=commit;h=dc7100f4080952798413fb63bb4134b22c57623a
I don't know if this is somehow connected to my problem ;)
> > But i don't know if that is correct way of disabling the cache.
>
> I don't remember the details, but I wouldn't think it is that simple.
> The Kirkwood manual would tell you. It is publicly available.
Unfortunately the Functional Specification doesn't mention anything about l2
caches. It references 'Unified Layer 2 (L2) Cache for Sheeva? CPU Cores
Addendum, Doc No. MV-S104858-U0', though, which isn't publicly availble i
guess.
Just for completeness, i'm now using the following to disable the l2 cache.
l2_cache_disable:
mrc p15, 1, r0, c15, c1, 0 @ marvell extra features register
bic r0, r0, #0x00400000 @ disable L2 cache
mcr p15, 1, r0, c15, c1, 0
mov pc, lr
Google finds some sourcecode for "marvell extra features register". And there
is of course arch/arm/mm/cache-feroceon-l2.c.
--
Michael
next prev parent reply other threads:[~2011-12-13 23:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201112112255.32534.michael@walle.cc>
2011-12-12 0:53 ` arm and patch phys offset Nicolas Pitre
2011-12-12 21:12 ` Michael Walle
2011-12-12 21:34 ` Russell King - ARM Linux
2011-12-12 21:55 ` Michael Walle
2011-12-12 22:02 ` Russell King - ARM Linux
2011-12-12 22:09 ` Michael Walle
2011-12-12 22:21 ` Russell King - ARM Linux
2011-12-12 22:56 ` Nicolas Pitre
2011-12-13 0:08 ` Michael Walle
2011-12-13 4:01 ` Nicolas Pitre
2011-12-13 23:17 ` Michael Walle [this message]
2011-12-18 11:58 ` Tixy
2012-01-03 7:15 ` Linus Walleij
2012-01-03 7:41 ` Michael Walle
2011-12-12 21:38 ` Nicolas Pitre
2011-12-12 21:57 ` Russell King - ARM Linux
2011-12-12 22:25 ` Nicolas Pitre
2011-12-12 22:06 ` Michael Walle
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=201112140017.49567.michael@walle.cc \
--to=michael@walle.cc \
--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.