From: Orjan Friberg <of@flatfrog.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: OMAP 3530 arch_shutdown "undefined instruction"
Date: Thu, 27 May 2010 13:03:27 +0200 [thread overview]
Message-ID: <4BFE517F.9050704@flatfrog.com> (raw)
In-Reply-To: <20100527093132.GC23664@pengutronix.de>
On 2010-05-27 11:31, Sascha Hauer wrote:
> Seems this does not work on Cortex Processors. Can you try replacing
> this with the following please:
>
> asm volatile (
> "bl __mmu_cache_flush;"
> "bl __mmu_cache_off;"
> :
> :
> : "r0", "r1", "r2", "r3", "r6", "r10", "r12", "cc", "memory"
> );
Thanks, this seems to work fine (in the sense that I can load and run a
second stage bootloader; I haven't tried verifying what happens with the
I and D cache).
--
Orjan Friberg
FlatFrog Laboratories AB
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-05-27 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 14:48 Orjan Friberg
2010-05-27 9:31 ` Sascha Hauer
2010-05-27 11:03 ` Orjan Friberg [this message]
2010-06-08 8:02 Luca Ceresoli
2010-06-10 12:22 ` Sascha Hauer
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=4BFE517F.9050704@flatfrog.com \
--to=of@flatfrog.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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