From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mark Guertin <mguertin@macdiscussion.com>
Cc: "qemu devel nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] vl on PPC ?
Date: Sun, 31 Aug 2003 20:28:14 +0200 [thread overview]
Message-ID: <1062354494.32739.56.camel@gaston> (raw)
In-Reply-To: <BB77A76A.1B33%mguertin@macdiscussion.com>
On Sun, 2003-08-31 at 19:23, Mark Guertin wrote:
> That was exactly it, works beautifully now. In fact booted into the
> provided 2.5 kernel and playing with some stuff right now.
>
> Is this generally safe to use (has the stuff Cort mentions in the comment
> been taken care of)?
It's safe on pmacs at least :) Some shitty embedded stuffs and PREP machines
still play mapping tricks between 0x80000000 and 0xc0000000, though most of
these are easily fixed.
Ben.
next prev parent reply other threads:[~2003-08-31 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 21:21 [Qemu-devel] vl on PPC ? Mark Guertin
2003-08-27 7:05 ` Benjamin Herrenschmidt
2003-08-27 18:07 ` Mark Guertin
2003-08-31 17:23 ` Mark Guertin
2003-08-31 18:28 ` Benjamin Herrenschmidt [this message]
2003-08-27 7:44 ` Benjamin Herrenschmidt
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=1062354494.32739.56.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=mguertin@macdiscussion.com \
--cc=qemu-devel@nongnu.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).