From: "Wohlgemuth, Jason" <jason_wohlgemuth@gilbarco.com>
To: "'linuxppc-dev@lists.linuxppc.org'" <linuxppc-dev@lists.linuxppc.org>
Subject: Kernel space question?
Date: Fri, 29 Oct 1999 09:05:25 -0400 [thread overview]
Message-ID: <199910291305.JAA24820@hoover.gilbarco.com> (raw)
Just a quick question... When I was working to get Linux running on a custom
MPC860, it was necessary to move the IMMR to 0xF??????? in order to avoid a
kernel panic after the VM was running. I understand the kernel has a
certain range of memory which is kernel space when the IMMR was at a lower
address it could not be directly accessed. Could someone explain to me the
exact size of kernel space and what the valid range of addresses can be
accessed outside it?
Thanks in advance,
Jason
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-10-29 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-29 13:05 Wohlgemuth, Jason [this message]
1999-10-29 17:07 ` Kernel space question? Dan Malek
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=199910291305.JAA24820@hoover.gilbarco.com \
--to=jason_wohlgemuth@gilbarco.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;
as well as URLs for NNTP newsgroup(s).