From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Stanislaw Skowronek <sskowron@ET.PUT.Poznan.PL>
Cc: Cameron Cooper <developer@phatlinux.com>, linux-mips@linux-mips.org
Subject: Re: Porting To New System
Date: Sat, 28 May 2005 00:12:47 +0100 [thread overview]
Message-ID: <1117235565.5730.255.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.GSO.4.10.10505272130200.1499-100000@helios.et.put.poznan.pl>
On Gwe, 2005-05-27 at 20:43, Stanislaw Skowronek wrote:
> Rest assured, there will be no MMU interface.
You seem remarkably confident for someone who has never taken one apart.
There are numerous ways to present an MMU interface without allowing
arbitary system access providing you do it via the core OS rather than
via the hardware. This is how Xen handles x86 and the same can be done
by other systems.
next prev parent reply other threads:[~2005-05-27 23:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 16:59 Porting To New System Cameron Cooper
2005-05-27 17:30 ` Stanislaw Skowronek
2005-05-27 18:13 ` Alan Cox
2005-05-27 18:21 ` Cameron Cooper
2005-05-27 19:43 ` Stanislaw Skowronek
2005-05-27 23:12 ` Alan Cox [this message]
2005-05-28 5:07 ` Stanislaw Skowronek
2005-05-28 7:30 ` Stanislaw Skowronek
2005-05-28 15:48 ` Cameron Cooper
2005-05-27 19:52 ` Cameron Cooper
2005-05-27 23:40 ` Alan Cox
2005-05-28 15:43 ` Cameron Cooper
2005-05-28 19:27 ` Ralf Baechle
2005-05-28 19:35 ` Cameron Cooper
-- strict thread matches above, loose matches on Subject: below --
2005-05-27 16:28 Cameron Cooper
2005-05-27 16:41 ` Alan Cox
2005-05-27 3:11 developer
2005-05-27 4:37 ` Stanislaw Skowronek
2005-05-27 5:13 ` Ed Okerson
2005-05-27 5:40 ` Stanislaw Skowronek
2005-05-27 6:22 ` Kumba
2005-05-27 22:51 ` Ralf Baechle
2005-05-28 19:43 ` Cameron Cooper
2005-05-28 19:50 ` Thiemo Seufer
2005-05-28 19:55 ` Ralf Baechle
2005-05-28 19:55 ` Cameron Cooper
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=1117235565.5730.255.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=developer@phatlinux.com \
--cc=linux-mips@linux-mips.org \
--cc=sskowron@ET.PUT.Poznan.PL \
/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