From: "Erik J. Green" <erik@greendragon.org>
To: linux-mips@linux-mips.org
Subject: Where does physical RAM start in kseg0?
Date: Sun, 13 Apr 2003 02:13:51 +0000 [thread overview]
Message-ID: <1050200031.3e98c7df2c227@my.visi.com> (raw)
Hi again, everyone;
A question about kseg0: Do system designers usually set things up such that
kseg0 begins at the start of physical memory, regardless of the xkphys offset at
which RAM starts?
Or is it necessary to add the offset at which RAM starts to the kseg0 base,
making it possible that the system designers could start RAM addresses high
enough (above 512M) to make kseg0 unusable? Does anyone have an implementation
in which this is the case?
If kseg0 provides a window beginning at physical address 0, that means I'm going
to try using Ralf's mapped kernel option, or I'll have to get the kernel up and
running in 64 bit only mode (I believe 32 bit compat binaries would still work,
since kuseg can be mapped).
Erik
--
Erik J. Green
erik@greendragon.org
next reply other threads:[~2003-04-13 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-13 2:13 Erik J. Green [this message]
2003-04-13 2:25 ` Where does physical RAM start in kseg0? Ralf Baechle
2003-04-13 2:28 ` Erik J. Green
2003-04-14 12:31 ` Maciej W. Rozycki
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=1050200031.3e98c7df2c227@my.visi.com \
--to=erik@greendragon.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox