From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: pbonzini@redhat.com, marcandre.lureau@redhat.com,
palmer@dabbelt.com, alistair.francis@wdc.com,
christoph.muellner@vrull.eu
Cc: liwei1518@gmail.com, daniel.barboza@oss.qualcomm.com,
zhiwei_liu@linux.alibaba.com, chao.liu.zevorn@gmail.com,
jserv@ccns.ncku.edu.tw, eleanor15x@gmail.com,
qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
Kuan-Wei Chiu <visitorckw@gmail.com>
Subject: [PATCH RFC 0/5] hw/riscv: Add support for Milk-V Duo board
Date: Tue, 12 May 2026 09:46:08 +0000 [thread overview]
Message-ID: <20260512094614.3464388-1-visitorckw@gmail.com> (raw)
Add initial support for the Milk-V Duo board.
This is something I've been playing around with in my local branch, and
I've reached a point where the implementation is enough to boot OpenSBI
and reach a Linux shell using an SD card image.
I am sending this as an RFC to get early feedback to understand the gap
between this minimal implementation and what is required for a upstream
merge. I plan to continue implementing missing blocks (like gpio and
clk/rst) in future.
Kuan-Wei Chiu (5):
target/riscv: Add stubs for T-Head PMU CSRs
hw/char: Add dw8250 UART
hw/misc: Add Sophgo CV1800B clock controller
hw/riscv: Add Sophgo CV1800B SoC support
hw/riscv: Add Milk-V Duo board support
MAINTAINERS | 11 ++
configs/devices/riscv64-softmmu/default.mak | 1 +
hw/char/Kconfig | 4 +
hw/char/dw8250.c | 118 ++++++++++++++
hw/char/meson.build | 1 +
hw/misc/Kconfig | 3 +
hw/misc/cv1800b_clk.c | 89 +++++++++++
hw/misc/meson.build | 1 +
hw/riscv/Kconfig | 14 ++
hw/riscv/cv1800b.c | 168 ++++++++++++++++++++
hw/riscv/meson.build | 3 +
hw/riscv/milkv_duo.c | 122 ++++++++++++++
include/hw/char/dw8250.h | 27 ++++
include/hw/misc/cv1800b_clk.h | 24 +++
include/hw/riscv/cv1800b.h | 52 ++++++
target/riscv/th_csr.c | 30 ++++
16 files changed, 668 insertions(+)
create mode 100644 hw/char/dw8250.c
create mode 100644 hw/misc/cv1800b_clk.c
create mode 100644 hw/riscv/cv1800b.c
create mode 100644 hw/riscv/milkv_duo.c
create mode 100644 include/hw/char/dw8250.h
create mode 100644 include/hw/misc/cv1800b_clk.h
create mode 100644 include/hw/riscv/cv1800b.h
--
2.54.0.563.g4f69b47b94-goog
next reply other threads:[~2026-05-12 9:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 9:46 Kuan-Wei Chiu [this message]
2026-05-12 9:46 ` [PATCH RFC 1/5] target/riscv: Add stubs for T-Head PMU CSRs Kuan-Wei Chiu
2026-05-13 2:13 ` Alistair Francis
2026-05-13 14:49 ` Kuan-Wei Chiu
2026-05-12 9:46 ` [PATCH RFC 2/5] hw/char: Add dw8250 UART Kuan-Wei Chiu
2026-05-12 9:46 ` [PATCH RFC 3/5] hw/misc: Add Sophgo CV1800B clock controller Kuan-Wei Chiu
2026-05-12 9:46 ` [PATCH RFC 4/5] hw/riscv: Add Sophgo CV1800B SoC support Kuan-Wei Chiu
2026-05-12 9:46 ` [PATCH RFC 5/5] hw/riscv: Add Milk-V Duo board support Kuan-Wei Chiu
2026-05-13 2:27 ` [PATCH RFC 0/5] hw/riscv: Add support for Milk-V Duo board Alistair Francis
2026-05-13 14:56 ` Kuan-Wei Chiu
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=20260512094614.3464388-1-visitorckw@gmail.com \
--to=visitorckw@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=chao.liu.zevorn@gmail.com \
--cc=christoph.muellner@vrull.eu \
--cc=daniel.barboza@oss.qualcomm.com \
--cc=eleanor15x@gmail.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=liwei1518@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.