From: Thomas Huth <huth@tuxfamily.org>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>,
Bryce Lanham <blanham@gmail.com>,
Natalia Portillo <claunia@claunia.com>
Subject: [Qemu-devel] [PATCH v1 0/4] m68k: Add basic support for the NeXTcube machine
Date: Sat, 30 Jun 2018 10:33:53 +0200 [thread overview]
Message-ID: <20180630083357.23489-1-huth@tuxfamily.org> (raw)
During Google Summer of Code 2011, Bryce Lanham added the possibility to
emulate the NeXTcube machine in QEMU, e.g. see this URL for some details:
https://wiki.qemu.org/Google_Summer_of_Code_2011#NeXT_machines_system_emulation
But since the machine requires a 68040 CPU and this was not included in
upstream QEMU in 2011 yet, the patches have never been merged to upstream.
Now in 2018, Laurent completed the full 680x0 support in upstream QEMU, so
we could finally merge the NeXTcube support, too.
The QEMU interfaces changed a lot since 2011, so I had to modify the
sources quite a bit, but with the attached patches, it is now possible
to boot up to the firmware monitor again.
Note that boot device emulation is either still missing (network), or
not working correctly yet (SCSI), so you can not boot any operating
systems with this machine yet.
Please ignore the checkpatch warnings about C99 "//" comments. There
are many of those in the sources, used to comment out alternative code
lines. I did not want to remove those yet, since some of them could
still be helpful while improving the machine emulation in the future.
Thomas Huth (4):
m68k: Add NeXTcube framebuffer device emulation
m68k: Add NeXTcube keyboard device
m68k: Add NeXTcube machine
m68k: Add an entry for the NeXTcube machine to the MAINTAINERS file
MAINTAINERS | 7 +
default-configs/m68k-softmmu.mak | 4 +
hw/display/Makefile.objs | 1 +
hw/display/next-fb.c | 152 ++++
hw/m68k/Makefile.objs | 5 +-
hw/m68k/next-cube.c | 1103 ++++++++++++++++++++++++++++++
hw/m68k/next-kbd.c | 289 ++++++++
include/hw/m68k/next-cube.h | 49 ++
8 files changed, 1608 insertions(+), 2 deletions(-)
create mode 100644 hw/display/next-fb.c
create mode 100644 hw/m68k/next-cube.c
create mode 100644 hw/m68k/next-kbd.c
create mode 100644 include/hw/m68k/next-cube.h
--
2.17.1
next reply other threads:[~2018-06-30 8:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 8:33 Thomas Huth [this message]
2018-06-30 8:33 ` [Qemu-devel] [PATCH v1 1/4] m68k: Add NeXTcube framebuffer device emulation Thomas Huth
2018-06-30 16:00 ` Richard Henderson
2018-06-30 16:12 ` Peter Maydell
2018-06-30 19:47 ` Thomas Huth
2018-06-30 20:06 ` Peter Maydell
2018-06-30 8:33 ` [Qemu-devel] [PATCH v1 2/4] m68k: Add NeXTcube keyboard device Thomas Huth
2018-06-30 16:18 ` Peter Maydell
2018-06-30 8:33 ` [Qemu-devel] [PATCH v1 4/4] m68k: Add an entry for the NeXTcube machine to the MAINTAINERS file Thomas Huth
2018-06-30 9:42 ` [Qemu-devel] [PATCH v1 0/4] m68k: Add basic support for the NeXTcube machine Mark Cave-Ayland
2018-06-30 13:14 ` Thomas Huth
2018-06-30 13:17 ` Peter Maydell
2018-06-30 13:34 ` Thomas Huth
2018-06-30 17:07 ` Bryce Lanham
2018-06-30 20:09 ` Thomas Huth
2018-07-03 20:58 ` Natalia Portillo
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=20180630083357.23489-1-huth@tuxfamily.org \
--to=huth@tuxfamily.org \
--cc=blanham@gmail.com \
--cc=claunia@claunia.com \
--cc=laurent@vivier.eu \
--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).