From: Thomas Glanzmann <thomas@glanzmann.de>
To: linuxppc-embedded@ozlabs.org
Subject: start_kernel does not get called on Virtex 4 FX 12 ppc 405
Date: Thu, 21 Jun 2007 14:33:03 +0200 [thread overview]
Message-ID: <20070621123303.GD27854@cip.informatik.uni-erlangen.de> (raw)
Hello,
I still have the problem that embedded kernel boot loader "load_kernel"
is working but "start_kernel" is never reached AFAIT. The last message
that I see is: "Now booting the kernel".
So I turned some LEDs on the Development board off in "load_kernel" and
tried to turn them back on in "start_kernel" I would like to know if
that still works. Or is not possible because the IO addresses are not
mapped via the MMU at the time. When I try to turn them back on in
"start_kernel"?
I used the following code:
*(volatile unsigned int *) (0x40000000 + 4) = 0x0;
__asm__ volatile ("eieio");
*(volatile unsigned int *) (0x40000000 + 0) = 0x0;
__asm__ volatile ("eieio");
First memory mapped io is direction register and the second call turns the leds
on/off. It works in the "load_kernel" routine.
Thomas
reply other threads:[~2007-06-21 12:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070621123303.GD27854@cip.informatik.uni-erlangen.de \
--to=thomas@glanzmann.de \
--cc=linuxppc-embedded@ozlabs.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).