From: Sascha Hauer <s.hauer@pengutronix.de>
To: Luca Ceresoli <list@lucaceresoli.net>
Cc: barebox@lists.infradead.org
Subject: Re: OMAP 3530 arch_shutdown "undefined instruction"
Date: Thu, 10 Jun 2010 14:22:42 +0200 [thread overview]
Message-ID: <20100610122242.GP20799@pengutronix.de> (raw)
In-Reply-To: <L3OROK$8E14E73C17D97B7C877E590EED33976C@aruba.it>
On Tue, Jun 08, 2010 at 10:02:44AM +0200, Luca Ceresoli wrote:
> Orjan Friberg wrote:> 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).
>
> Works for me as well.
> Is it going to be committed?
Ok, done.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-06-10 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 8:02 OMAP 3530 arch_shutdown "undefined instruction" Luca Ceresoli
2010-06-10 12:22 ` Sascha Hauer [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-26 14:48 Orjan Friberg
2010-05-27 9:31 ` Sascha Hauer
2010-05-27 11:03 ` Orjan Friberg
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=20100610122242.GP20799@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=list@lucaceresoli.net \
/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.