From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PPC emulation on Qemu
Date: Mon, 16 Feb 2004 15:08:57 +1100 [thread overview]
Message-ID: <1076904537.6960.193.camel@gaston> (raw)
In-Reply-To: <1076902475.28421.2137.camel@rapid>
> Well, I did look a lot MOL code but didn't use it for now. I won't reuse
> MOL OF code, because I don't want to have hardcoded stuffs, but
> something that acts really like the open-firmware and will be able to
> boot any OS, just like Bochs BIOS does for PC's.
Latest "devel" tree from Samuel started integrating OpenBIOS in MOL
(that is a full OF implementation).
> But emulated hardware from MOL will be helpfull someday. For now, I want
> to concentrate on booting Linux for Prep hardware. Because it's mainly a
> PC with a PPC CPU, it's a real good target to debug CPU emulation
> problems without taking care of emulated hardware.
It's also the shitties PPC hardware out there ;) Instane memory map
> Then, I want a standard and nowedays PPC platform, not only Macs, nea
> OpenPPC standard.
What is OpenPPC standard ? So far, the most "standard" PPCs are
PowerMacs ;)
> So I did an open-pic emulation, ... MOL code will be helpfull
> to emulate some Mac platforms, but as it says, it seems to me that's
> it's too much Mac & MacOS dedicated to help until I got full stable
> basics.
It can run the linux kernel as well. It's oriented toward emulation
speed though. It has this nice "OSI" calls mecanism that allows
cross call from within the emulated environment to the emulator
linux-side. That along with host-side drivers using these calls
allows significant perfs. improvements for things like disk
access, sound, etc... but that's all optional.
Ben
next prev parent reply other threads:[~2004-02-16 4:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 11:17 [Qemu-devel] PPC emulation on Qemu Manish Bansal
2004-02-15 14:07 ` J. Mayer
2004-02-15 14:59 ` Gabriel Ebner
2004-02-15 16:06 ` J. Mayer
2004-02-15 22:44 ` Benjamin Herrenschmidt
2004-02-16 3:34 ` J. Mayer
2004-02-16 4:08 ` Benjamin Herrenschmidt [this message]
2004-02-16 4:27 ` J. Mayer
2004-02-16 7:09 ` Benjamin Herrenschmidt
2004-02-18 9:42 ` J. Mayer
2004-02-18 10:35 ` J. Fortmann
2004-02-18 13:20 ` Jocelyn Mayer
2004-02-18 23:13 ` Benjamin Herrenschmidt
2004-02-19 0:59 ` J. Mayer
2004-02-19 1:57 ` Benjamin Herrenschmidt
2004-02-19 2:32 ` J. Mayer
2004-02-19 2:48 ` Benjamin Herrenschmidt
2004-02-19 3:33 ` J. Mayer
2004-02-19 4:27 ` Benjamin Herrenschmidt
2004-02-16 7:20 ` Gwenole Beauchesne
2004-02-16 7:46 ` Chad Page
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=1076904537.6960.193.camel@gaston \
--to=benh@kernel.crashing.org \
--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).