From: Phil Thompson <philt@4bridgeworks.com>
To: "'linuxppc-dev@lists.linuxppc.org'" <linuxppc-dev@lists.linuxppc.org>
Subject: What Bootloader Initialisation does the PPC Kernel Expect?
Date: Thu, 1 Apr 2004 16:58:32 +0100 [thread overview]
Message-ID: <C18BA5DDB58DD511BD0700C0DF0DD45028B291@NTSERVER4> (raw)
Hi,
I am porting the latest 2.4 kernel to a 405GP based board (using the Walnut
port as a reference). The bootloader is in-house code with minimal
functionality.
The kernel gets as far as displaying the "Now booting the kernel" message.
The actual line of code at which the kernel "disappears" is the "rfi"
instruction (in ppc/kernel/head_4xx.S) that is supposed to transfer control
to the "start_here" label, ie. when the MMU is enabled.
By this time, the kernel has executed very little board specific code, so
I'm thinking that the problem is that the bootloader might not be doing some
initialisation that the kernel is expecting.
Are there things that the kernel expects the bootloader to have done
(ignoring obvious things like setting up the memory controller)? Does the
above problem suggest anything in particular?
Many thanks,
Phil
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2004-04-01 15:58 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=C18BA5DDB58DD511BD0700C0DF0DD45028B291@NTSERVER4 \
--to=philt@4bridgeworks.com \
--cc=linuxppc-dev@lists.linuxppc.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