From: Adam Nielsen <a.nielsen@shikadi.net>
To: linux-mips@linux-mips.org
Subject: Setting the physical RAM map
Date: Sun, 29 Nov 2009 00:38:55 +1000 [thread overview]
Message-ID: <4B1135FF.9050908@shikadi.net> (raw)
Hi all,
I'm attempting to port the Linux kernel to an NCD HMX, an R4600-based X-Terminal.
I've currently got it to the point where it will download the kernel and
execute it, and start printing some messages out on the screen.
It gets as far as printing the physical RAM map and then crashes, but I'm not
sure why:
Determined physical RAM map:
memory: 00800000 @ 40250000 (usable)
memory: 00040000 @ 9fc00000 (ROM data)
Wasting 8407552 bytes for tracking 262736 unused pages
TLB refill exception PC = 40024094 address = 7FFFF000
The last message is from the boot monitor (the kernel is loaded at address
0x40020000.) I'm just guessing with the memory map, but I've tried lots of
different values with the same result, and I'm fairly sure there is RAM mapped
to the address I have used above (it's after the end of the kernel.) At any
rate the error message is from a completely different address, and it still
happens if I flag that area as reserved memory in the RAM map.
Some of the MIPS devices don't seem to have code to create a memory map, so
I'm wondering whether this is necessary or if there's a generic MIPS way to
retrieve the current mapping.
Also, if anyone has any ideas what the kernel is trying to do accessing that
invalid address I could use some hints!
Many thanks,
Adam.
next reply other threads:[~2009-11-28 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-28 14:38 Adam Nielsen [this message]
2009-11-30 19:00 ` Setting the physical RAM map David VomLehn
2009-11-30 19:25 ` Geert Uytterhoeven
2009-11-30 22:35 ` Adam Nielsen
2009-12-20 9:07 ` Adam Nielsen
2009-11-30 21:41 ` Ralf Baechle
2009-11-30 22:38 ` Adam Nielsen
2009-12-01 0:49 ` Ralf Baechle
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=4B1135FF.9050908@shikadi.net \
--to=a.nielsen@shikadi.net \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.