From: Daniel Palmer <daniel@thingy.jp>
To: visitorckw@gmail.com, angelo@kernel-space.org, bmeng.cn@gmail.com
Cc: laurent@vivier.eu, u-boot@lists.denx.de,
Daniel Palmer <daniel@thingy.jp>
Subject: [RFC PATCH 0/3] Add virtio-mmio support to m68k virt machine
Date: Tue, 10 Mar 2026 22:59:37 +0900 [thread overview]
Message-ID: <20260310135940.1756141-1-daniel@thingy.jp> (raw)
Lets start making the m68k virt machine support useful.
This allows the virtio mmio driver instances to be created with
platform data, fixes (for some value of fix) the endian issues in
virtio mmio and then adds the code for the board to create the
instances.
This is very rough. I'm not sure how to fix the endian issues or
if there are even any issues and I missed something. I got my
version of the m68k virt machine working back in 2024 and can't
remember everything.
Daniel Palmer (3):
virtio: mmio: Allow instantiation via platform data
virtio: mmio: endian *fixes* *HACK*
board: qemu: m68k: Create virtio mmio instances
arch/m68k/Kconfig | 14 +--
board/emulation/qemu-m68k/qemu-m68k.c | 46 +++++++++
drivers/virtio/virtio_mmio.c | 141 ++++++++++++++++----------
include/virtio_mmio.h | 12 +++
4 files changed, 152 insertions(+), 61 deletions(-)
create mode 100644 include/virtio_mmio.h
--
2.51.0
next reply other threads:[~2026-03-10 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 13:59 Daniel Palmer [this message]
2026-03-10 13:59 ` [RFC PATCH 1/3] virtio: mmio: Allow instantiation via platform data Daniel Palmer
2026-03-10 13:59 ` [RFC PATCH 2/3] virtio: mmio: endian *fixes* *HACK* Daniel Palmer
2026-03-14 8:53 ` Daniel Palmer
2026-04-02 19:43 ` Kuan-Wei Chiu
2026-04-04 1:49 ` Daniel Palmer
2026-03-10 13:59 ` [RFC PATCH 3/3] board: qemu: m68k: Create virtio mmio instances Daniel Palmer
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=20260310135940.1756141-1-daniel@thingy.jp \
--to=daniel@thingy.jp \
--cc=angelo@kernel-space.org \
--cc=bmeng.cn@gmail.com \
--cc=laurent@vivier.eu \
--cc=u-boot@lists.denx.de \
--cc=visitorckw@gmail.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