From: Thomas Huth <huth@tuxfamily.org>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/8] Add the m68k next-cube machine
Date: Sat, 7 Sep 2019 17:47:36 +0200 [thread overview]
Message-ID: <20190907154744.4136-1-huth@tuxfamily.org> (raw)
Hi Peter,
the following changes since commit 90b1e3afd33226b6078fec6d77a18373712a975c:
Merge remote-tracking branch 'remotes/huth-gitlab/tags/pull-request-2019-09-05-v2' into staging (2019-09-05 17:09:13 +0100)
are available in the Git repository at:
https://gitlab.com/huth/qemu.git tags/m68k-pull-2019-09-07
for you to fetch changes up to 25311649592f5584b1e1012d69c7327ef87473f4:
.travis.yml: Let the avocado job run the NeXTcube tests (2019-09-07 08:35:41 +0200)
----------------------------------------------------------------
Add the m68k next-cube machine
----------------------------------------------------------------
Laurent Vivier (1):
escc: introduce a selector for the register bit
Philippe Mathieu-Daudé (2):
tests/acceptance: Add test of NeXTcube framebuffer using OCR
.travis.yml: Let the avocado job run the NeXTcube tests
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
.travis.yml | 7 +-
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/acceptance/machine_m68k_nextcube.py | 121 ++++
tests/boot-serial-test.c | 12 +
14 files changed, 1641 insertions(+), 7 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
create mode 100644 tests/acceptance/machine_m68k_nextcube.py
next reply other threads:[~2019-09-07 15:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 15:47 Thomas Huth [this message]
2019-09-07 15:47 ` [Qemu-devel] [PULL 1/8] m68k: Add NeXTcube framebuffer device emulation Thomas Huth
2019-09-07 15:47 ` [Qemu-devel] [PULL 2/8] m68k: Add NeXTcube keyboard device Thomas Huth
2019-09-07 15:47 ` [Qemu-devel] [PULL 3/8] m68k: Add NeXTcube machine Thomas Huth
2019-09-16 10:48 ` Peter Maydell
2019-09-18 9:27 ` Thomas Huth
2019-09-07 15:47 ` [Qemu-devel] [PULL 4/8] escc: introduce a selector for the register bit Thomas Huth
2019-09-07 15:47 ` [Qemu-devel] [PULL 5/8] m68k: Add serial controller to the NeXTcube machine Thomas Huth
2019-09-07 15:47 ` [Qemu-devel] [PULL 6/8] m68k: Add an entry for the NeXTcube machine to the MAINTAINERS file Thomas Huth
2019-09-07 15:47 ` [Qemu-devel] [PULL 7/8] tests/acceptance: Add test of NeXTcube framebuffer using OCR Thomas Huth
2019-09-10 12:02 ` Peter Maydell
2019-09-10 12:07 ` Thomas Huth
2019-09-10 12:58 ` Philippe Mathieu-Daudé
2019-09-07 15:47 ` [Qemu-devel] [PULL 8/8] .travis.yml: Let the avocado job run the NeXTcube tests Thomas Huth
2019-09-09 14:43 ` [Qemu-devel] [PULL 0/8] Add the m68k next-cube machine Peter Maydell
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=20190907154744.4136-1-huth@tuxfamily.org \
--to=huth@tuxfamily.org \
--cc=peter.maydell@linaro.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).