From: 'Sascha Hauer' <s.hauer@pengutronix.de>
To: Marc Reilly <marc@cpdesign.com.au>
Cc: barebox@lists.infradead.org
Subject: Re: booting uImage for mx35 3stack
Date: Thu, 15 Apr 2010 10:05:46 +0200 [thread overview]
Message-ID: <20100415080546.GN7882@pengutronix.de> (raw)
In-Reply-To: <003401cadc50$ba662070$2f326150$@cpdesign.com.au>
On Thu, Apr 15, 2010 at 02:04:16PM +1000, Marc Reilly wrote:
> Hi Sascha,
>
> Thanks for all your help, and speedy responses.
>
> > > Nothing happens after "done, booting the kernel" (boot snippet at end
> > > of
> > > email)
> >
> > Newer kernels have earlyprintk support that could be of help here.
> > Please apply commit-id 93fd03a8c6728b58879f8af20ffd55d9c32a778b to your
> > kernel and add 'earlyprintk' to your kernel command line.
>
> Great tip. It shows the kernel is starting ok and getting stuck just after
> irqs are enabled.
> I'm still a bit baffled as to why this only happens with barebox.
Sounds somewhat familiar. I have just tested 2.6.31 and
2.6.34-rc-something on my board, both working fine.
Maybe this has something to do with the clocks. You could check the
register values of the CCM module in barebox and U-Boot
(md 0x53f80000+0x80).
Also note this mail:
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-April/012691.html
I suspect a bug in the kernel there which is still present.
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
prev parent reply other threads:[~2010-04-15 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 8:19 Marc Reilly
2010-04-14 8:37 ` Sascha Hauer
2010-04-15 4:04 ` Marc Reilly
2010-04-15 8:05 ` 'Sascha Hauer' [this message]
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=20100415080546.GN7882@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=marc@cpdesign.com.au \
/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