From: "David H. Lynch Jr" <dhlii@comcast.net>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Need help Understanding initial memory conditions.
Date: Tue, 18 Oct 2005 04:04:08 -0400 [thread overview]
Message-ID: <4354AC78.5080206@comcast.net> (raw)
What exactly is the minimal startup system state the Linux 2.6.13
Kernel expects ?
I am trying to bring up a xilinx V4 ppc 405 board.
It has flash based at 0x0 and DRAM based at ox98000000.
I already have a working monitor/program loader and a filesystem of
the flash. I can fairly easily compile and load onto the filesystem and
run standalone PPC apps on the board.
All memory is as configured by the base hardware. The MMU, BAT, ...
are all at their powerup state.
I have put together a Linux config based heavily on an abbreviated
version of the Xilinx ML-300 config.
If I try to load it it just goes bye-bye.
I am trying to decipher the initial machine state Linux 2.6.13 expects.
u-boot seems to completely setup the MMU, but also seems to expect
to start execution from flash or ROM.
scanning the Linux code seems to indicate that the only entry that
needs to be setup for the MMU is the one for block Linux starts
executing out of.
I am also being somewhat confused by references to physical address
0 and virtual address 0xc000000.
I thought Linux executed from virtual address 0, and the actual
physical address was a function of the hardware.
next reply other threads:[~2005-10-18 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 8:04 David H. Lynch Jr [this message]
2005-10-18 8:49 ` Need help Understanding initial memory conditions Kalle Pokki
2005-10-18 19:15 ` David H. Lynch Jr.
2005-10-18 20:14 ` Kalle Pokki
2005-10-19 5:16 ` David H. Lynch Jr
2005-10-19 6:37 ` Kalle Pokki
2005-10-19 10:24 ` Andrei Konovalov
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=4354AC78.5080206@comcast.net \
--to=dhlii@comcast.net \
--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).