From: Dan Malek <dan@mvista.com>
To: Okehee Goh <ogoh@asu.edu>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MMU in MBX860
Date: Thu, 25 Oct 2001 11:19:38 -0400 [thread overview]
Message-ID: <3BD82D8A.F0DC3B77@mvista.com> (raw)
In-Reply-To: AEEDJHMEPHBIHBAHOOCDIELKCAAA.ogoh@asu.edu
Okehee Goh wrote:
> The problem is that it shares one global page table between kernel and
> application processes.
You can support any type of memory mapping and protection you wish using a
combination of features supported by the 8xx MMU and standard operating
system mapping techniques. What you are asking to do isn't difficult, but
asking us to design your system for you in a reasonable period of time
isn't likely to happen on this mailing list :-).
Good Luck.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-25 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 22:46 MMU in MBX860 Okehee Goh
2001-10-25 4:01 ` Dan Malek
2001-10-25 4:51 ` Okehee Goh
2001-10-25 15:19 ` Dan Malek [this message]
2001-10-25 15:45 ` 405GP Dhrystone Benchmark ibm405.linux
2001-10-25 16:26 ` Mark Hatle
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=3BD82D8A.F0DC3B77@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=ogoh@asu.edu \
/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).