public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Daniel Palmer <daniel@thingy.jp>
To: visitorckw@gmail.com, angelo@kernel-space.org, bmeng.cn@gmail.com
Cc: u-boot@lists.denx.de, Daniel Palmer <daniel@thingy.jp>
Subject: [PATCH v3 0/5] Add virtio-mmio support to m68k virt machine
Date: Thu,  9 Apr 2026 07:09:23 +0900	[thread overview]
Message-ID: <20260408220928.3328551-1-daniel@thingy.jp> (raw)

Lets start making the m68k virt machine support useful.

First we need to fix some m68k endian issues.

Then allow virtio mmio driver instances to be created with
platform data and fix a minor endian issue.

Finally, add the code for the board to create the instances.

v3:
  - Fix the bug with the vendor string in virtio-blk properly,
    this removes the last endian hack in virtio-mmio
  - Leave the current behaviour for readl() for coldfire as it
    breaks thing.

v2:
  - Added patch to fix readl() etc on m68k, hopefully this
    doesn't break everything. This should match Linux now.
  - Added patch to fix sys reset which is broken by the above
  - Hacks to virtio-mmio are gone because they aren't needed
    anymore, just one minor endian fix now.
  - Removed RFC because it looks good to me*.


* I wouldn't trust me. :)

Daniel Palmer (5):
  sysreset: qemu virt: Use __raw_writel()
  m68k: Fix writew(), writel(), readw(), readl() endianness for classic
    m68k
  virtio: mmio: Allow instantiation via platform data
  virtio: blk: Fix converting the vendor id to a string
  board: qemu: m68k: Create virtio mmio instances

 arch/m68k/Kconfig                          | 14 ++++---
 arch/m68k/include/asm/io.h                 | 31 +++++++++-----
 board/emulation/qemu-m68k/qemu-m68k.c      | 47 ++++++++++++++++++++++
 drivers/sysreset/sysreset_qemu_virt_ctrl.c |  2 +-
 drivers/virtio/virtio_blk.c                | 12 +++---
 drivers/virtio/virtio_mmio.c               | 27 ++++++++-----
 include/virtio_mmio.h                      | 14 +++++++
 7 files changed, 113 insertions(+), 34 deletions(-)
 create mode 100644 include/virtio_mmio.h

-- 
2.51.0


             reply	other threads:[~2026-04-08 22:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08 22:09 Daniel Palmer [this message]
2026-04-08 22:09 ` [PATCH v3 1/5] sysreset: qemu virt: Use __raw_writel() Daniel Palmer
2026-04-11 16:28   ` Simon Glass
2026-04-11 19:40   ` Angelo Dureghello
2026-04-08 22:09 ` [PATCH v3 2/5] m68k: Fix writew(), writel(), readw(), readl() endianness for classic m68k Daniel Palmer
2026-04-11 16:28   ` Simon Glass
2026-04-11 21:07   ` Angelo Dureghello
2026-04-12  0:59     ` Daniel Palmer
2026-04-08 22:09 ` [PATCH v3 3/5] virtio: mmio: Allow instantiation via platform data Daniel Palmer
2026-04-11 16:28   ` Simon Glass
2026-04-11 21:15   ` Angelo Dureghello
2026-04-12  5:12     ` Daniel Palmer
2026-04-08 22:09 ` [PATCH v3 4/5] virtio: blk: Fix converting the vendor id to a string Daniel Palmer
2026-04-11 20:30   ` Simon Glass
2026-04-08 22:09 ` [PATCH v3 5/5] board: qemu: m68k: Create virtio mmio instances Daniel Palmer
2026-04-11 20:28   ` Angelo Dureghello
2026-04-12  6:42     ` Daniel Palmer
2026-04-11 20:31   ` Simon Glass

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=20260408220928.3328551-1-daniel@thingy.jp \
    --to=daniel@thingy.jp \
    --cc=angelo@kernel-space.org \
    --cc=bmeng.cn@gmail.com \
    --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