From: michael@walle.cc (Michael Walle)
To: linux-arm-kernel@lists.infradead.org
Subject: arm and patch phys offset
Date: Tue, 3 Jan 2012 08:41:22 +0100 [thread overview]
Message-ID: <9ba2ef7841feed31c5e4f05a06a7d3ea.squirrel@ssl.serverraum.org> (raw)
In-Reply-To: <CACRpkdZ5V7KgWpLRPZ8yV9p_80gmjibH0EokZ3MoYktpOQssxw@mail.gmail.com>
Hi Linus,
On Tue, January 3, 2012 08:15, Linus Walleij wrote:
> On Tue, Dec 13, 2011 at 1:08 AM, Michael Walle <michael@walle.cc> wrote:
>
>> Seems like the l2 cache is enabled after uboot starts the linux kernel.
>> I'll
>> dig deeper into that tomorrow.
>
> Try to disable both L2 and L1 cach in U-Boot. That has solved
> similar issues for me.
>
> In include/configs/my_board.h
>
> #define CONFIG_SYS_DCACHE_OFF
but also slow things down in uboot, doesnt it? I've posted a patch on the
uboot ml which disables the l2 cache upon linux start.
http://patchwork.ozlabs.org/patch/132533/
You could try that, too.
--
michael
next prev parent reply other threads:[~2012-01-03 7:41 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
2011-12-18 11:58 ` Tixy
2012-01-03 7:15 ` Linus Walleij
2012-01-03 7:41 ` Michael Walle [this message]
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=9ba2ef7841feed31c5e4f05a06a7d3ea.squirrel@ssl.serverraum.org \
--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 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).