From: "Hervé Poussineau" <hpoussin@reactos.org>
To: qemu-devel@nongnu.org
Cc: "David Gibson" <david@gibson.dropbear.id.au>,
"Alexander Graf" <agraf@suse.de>,
qemu-ppc@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
"Giancarlo Teodori" <gteodori@gmail.com>,
"Hervé Poussineau" <hpoussin@reactos.org>
Subject: [Qemu-devel] [PATCH v3 0/4] ppc: add a IBM 40p machine (RS/6000, PReP)
Date: Sat, 7 Jan 2017 16:23:39 +0100 [thread overview]
Message-ID: <1483802623-5507-1-git-send-email-hpoussin@reactos.org> (raw)
Hi,
This patchset adds the emulation of the IBM RS/6000 7020 (40p). The real machine is
able to run AIX (up to 4.3.3), Windows NT (up to 4.0 SP1), the beta of OS/2 PowerPC,
Solaris, Linux, NetBSD/PReP ...
I've tested current emulation with Open Hack'Ware, OpenBIOS and official firmware.
Linux kernel starts, and freezes during boot (seems like a problem with the SCSI adapter).
Windows NT starts up to the point where it wants to change endianness.
Other OSes have not been tested.
This machine is a superset of the 'prep' one, because we know exactly what is/should
emulated, and that operating system list running on it is quite wide.
I hope that 'prep' machine can be deprecated soon and then later removed.
Patch 1 is a cleanup, and can probably be committed first.
Patches 2 to 4 are the real implementation of the IBM 40p.
Changes since v2:
- patch 2: fix mismatch between read and write functions for port 92
- patch 4: use error_report instead of fprintf/hw_error
Changes since v1:
- removed patches related to display adapter:
Let's wait for an emulation of the real display adapter (an S3 Trio), as current
VGA adapter already mostly works with Open Hack'Ware and OpenBIOS
- various changes due to David Gibson's remarks
Hervé Poussineau (4):
prep: do not use global variable to access nvram
prep: add PReP System I/O
prep: add IBM RS/6000 7020 (40p) memory controller
prep: add IBM RS/6000 7020 (40p) machine emulation
default-configs/ppc-softmmu.mak | 2 +
hw/ppc/Makefile.objs | 2 +
hw/ppc/prep.c | 233 +++++++++++++++++++++++++++++-
hw/ppc/prep_systemio.c | 303 ++++++++++++++++++++++++++++++++++++++++
hw/ppc/rs6000_mc.c | 232 ++++++++++++++++++++++++++++++
hw/ppc/trace-events | 11 ++
6 files changed, 781 insertions(+), 2 deletions(-)
create mode 100644 hw/ppc/prep_systemio.c
create mode 100644 hw/ppc/rs6000_mc.c
--
2.1.4
next reply other threads:[~2017-01-07 15:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 15:23 Hervé Poussineau [this message]
2017-01-07 15:23 ` [Qemu-devel] [PATCH v3 1/4] prep: do not use global variable to access nvram Hervé Poussineau
2017-01-07 15:23 ` [Qemu-devel] [PATCH v3 2/4] prep: add PReP System I/O Hervé Poussineau
2017-01-07 15:23 ` [Qemu-devel] [PATCH v3 3/4] prep: add IBM RS/6000 7020 (40p) memory controller Hervé Poussineau
2017-01-07 15:23 ` [Qemu-devel] [PATCH v3 4/4] prep: add IBM RS/6000 7020 (40p) machine emulation Hervé Poussineau
2017-01-09 12:25 ` [Qemu-devel] [Qemu-ppc] " Thomas Huth
2017-01-10 20:51 ` Hervé Poussineau
2017-01-09 1:42 ` [Qemu-devel] [PATCH v3 0/4] ppc: add a IBM 40p machine (RS/6000, PReP) David Gibson
2017-01-09 7:43 ` [Qemu-devel] [Qemu-ppc] " Thomas Huth
2017-01-10 0:28 ` David Gibson
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=1483802623-5507-1-git-send-email-hpoussin@reactos.org \
--to=hpoussin@reactos.org \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=gteodori@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/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).