From: Sascha Hauer <s.hauer@pengutronix.de>
To: Nishanth Menon <menon.nishanth@gmail.com>
Cc: barebox@lists.infradead.org, Michael Grzeschik <mgr@pengutronix.de>
Subject: Re: omap3: omap3530_beagle_per_uart_defconfig broken
Date: Tue, 17 Aug 2010 08:35:54 +0200 [thread overview]
Message-ID: <20100817063554.GR27749@pengutronix.de> (raw)
In-Reply-To: <4C6A074A.4050606@gmail.com>
On Mon, Aug 16, 2010 at 10:51:38PM -0500, Nishanth Menon wrote:
> Hi,
> while just giving the omap3530 boot from internal sram a whirl, found that
>
> commit 78104ae181f78d83664fdc7522eb632d9c3b2ec9
> Author: Sascha Hauer <s.hauer@pengutronix.de>
> Date: Fri Apr 16 15:50:30 2010 +0200
>
> arm: reimplement startup code in C
>
> Lets translate the startup code to a language we all understand better.
> Tested on pcm038 (arm v5) and pcm043 (arm v6).
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
>
> broke the support for OMAP3530 internal boot capability -> it looks like
> many of the V7Dcache skip logic got dropped off in the patch. will try
> to fix it ahead.. reverting this commit helps the barebox master..
We worked on Omap lately. I remember that there was a problem with the
call to arch_init_lowlevel. Michael, do you have input on this?
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-08-17 6:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 3:51 Nishanth Menon
2010-08-17 6:35 ` Sascha Hauer [this message]
2010-08-17 6:50 ` Sascha Hauer
2010-08-17 10:09 ` Nishanth Menon
2010-08-17 11:25 ` 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=20100817063554.GR27749@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=menon.nishanth@gmail.com \
--cc=mgr@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