[v5,0/6] m68k: Add basic support for the NeXTcube machine

Message

Thomas Huth Aug. 31, 2019, 7:45 a.m. UTC

During Google Summer of Code 2011, Bryce Lanham added the possibility to
emulate the NeXTcube machine in QEMU, e.g. see these URLs for some details:

https://wiki.qemu.org/Google_Summer_of_Code_2011#NeXT_machines_system_emulation
https://lists.gnu.org/archive/html/qemu-devel/2011-08/msg02158.html

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.

Then, during the last years, 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 still missing (network and SCSI),
so you can not boot any operating systems with this machine yet. I have
the patches for these devices in my brach here:

 https://gitlab.com/huth/qemu/commits/next-cube

... but they are not quite working yet, so I'll submit them later once
they have been fixed and the basic support patches of this series have
been merged.

v5:
 - Rebased to master (fix the #include statements after Markus' rework)
 - Removed some more disabled/commented code fragments
 - Added Reviewed-bys and Tested-bys from Philippe
 - Mark the KBD device as unmigratable (m68k CPUs can not be migrated, too)

v4:
 - Fixed the "bmap" memory region with its alias - the error messages
   about wrong DIMMs should now be gone.
 - Managed to wired up the ESCC serial device (after including Laurent's
   "bit_swap" patch)

v3:
 - Don't connect the devices to the sysbus from the device files themselves,
   do it from next-cube.c instead.
 - Adjusted some values according to Philippe's review comments
 - The MMIO region at 0x820c0020 is now correctly initialized as alias
 - Some more clean-ups here and there

v2:
 - Don't use memory_region_allocate_system_memory() for the framebuffer
   device anymore
 - Turn the keyboard device into a proper QOM device
 - Put the global variables in the third patch into the machine state
   structure
 - Got rid of the "//" C++ comments

Laurent Vivier (1):
  escc: introduce a selector for the register bit

Thomas Huth (5):
  m68k: Add NeXTcube framebuffer device emulation
  m68k: Add NeXTcube keyboard device
  m68k: Add NeXTcube machine
  m68k: Add serial controller to the NeXTcube machine
  m68k: Add an entry for the NeXTcube machine to the MAINTAINERS file

 MAINTAINERS                      |   7 +
 default-configs/m68k-softmmu.mak |   1 +
 hw/char/escc.c                   |  30 +-
 hw/display/Makefile.objs         |   1 +
 hw/display/next-fb.c             | 146 +++++
 hw/m68k/Kconfig                  |   5 +
 hw/m68k/Makefile.objs            |   1 +
 hw/m68k/next-cube.c              | 978 +++++++++++++++++++++++++++++++
 hw/m68k/next-kbd.c               | 291 +++++++++
 include/hw/char/escc.h           |   1 +
 include/hw/m68k/next-cube.h      |  47 ++
 tests/boot-serial-test.c         |  12 +
 12 files changed, 1514 insertions(+), 6 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