From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: Daniel Palmer <daniel@0x0f.com>
Cc: Tom Rini <trini@konsulko.com>,
alison.wang@nxp.com, angelo@kernel-space.org,
jserv@ccns.ncku.edu.tw, eleanor15x@gmail.com,
u-boot@lists.denx.de
Subject: Re: [PATCH 0/3] m68k: Add support for QEMU virt machine
Date: Mon, 22 Dec 2025 16:44:41 +0800 [thread overview]
Message-ID: <aUkE-dvbDyZA_Ewy@google.com> (raw)
In-Reply-To: <CAFr9PXkk3eOYDZbjTvZPgT8Cv+Wd-+hiEA+hPZVOVD0BJZ378A@mail.gmail.com>
Hi Daniel,
On Sun, Dec 21, 2025 at 01:15:18PM +0900, Daniel Palmer wrote:
> Hi Tom, Kuan-Wei,
>
> On Fri, 19 Dec 2025 at 04:01, Tom Rini <trini@konsulko.com> wrote:
> >
> > On Thu, Dec 18, 2025 at 06:52:49PM +0000, Kuan-Wei Chiu wrote:
> > > Add support for the QEMU 'virt' machine on the m68k architecture. The
> > > QEMU virt machine models a generic system based on the Motorola 68040
> > > CPU and utilizes Goldfish virtual peripherals.
>
> > Well this is neat.
>
> I have had a messy version[0] of this that runs on 68000, 68030 and
> 68040 real hardware and virt for years..
> I thought no one would want it so never sent it.
>
> I have devicetree for 000 and code to create bootinfo so that linux
> can boot on 020+ machines.
> Gist of probably the oldest cpu that can run the latest u-boot[1]
>
> Can we work on this together to reduce duplication?
>
> 0 - https://github.com/fifteenhex/u-boot/tree/mc68000
> 1 - https://gist.github.com/fifteenhex/eed03b250b6a0113ab08b69be0375aa1
Wow, this is fantastic! I wasn't aware that you had already done so
much work on this. I would love to collaborate.
However, I noticed that your branch contains over 100+ commits with a
diff exceeding 15k+ lines. Attempting to integrate such a massive
amount of code directly into this v2 series would be extremely
difficult and likely overwhelming for the review process.
My current goal with this patch series is to establish a minimal
baseline support for m68k in U-Boot (targeting QEMU 040 first). I think
the best approach would be to get this foundational series merged first
to serve as a minimal base, and I am more than willing to make
adjustments in this series to facilitate the future integration of your
work (000/030 support, Linux bootinfo handling, etc.) incrementally.
What do you think?
Regards,
Kuan-Wei
next prev parent reply other threads:[~2025-12-22 13:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 18:52 [PATCH 0/3] m68k: Add support for QEMU virt machine Kuan-Wei Chiu
2025-12-18 18:52 ` [PATCH 1/3] serial: Add Goldfish TTY driver Kuan-Wei Chiu
2025-12-19 3:14 ` Yao Zi
2025-12-20 16:28 ` Kuan-Wei Chiu
2025-12-21 2:58 ` Yao Zi
2025-12-18 18:52 ` [PATCH 2/3] m68k: Add support for M68040 CPU Kuan-Wei Chiu
2025-12-18 19:00 ` Tom Rini
2025-12-20 16:43 ` Kuan-Wei Chiu
2025-12-22 16:20 ` Tom Rini
2025-12-21 4:53 ` Daniel Palmer
2025-12-21 7:25 ` Angelo Dureghello
2025-12-22 9:21 ` Kuan-Wei Chiu
2025-12-18 18:52 ` [PATCH 3/3] board: Add QEMU m68k virt board support Kuan-Wei Chiu
2025-12-18 19:04 ` Tom Rini
2025-12-20 16:48 ` Kuan-Wei Chiu
2025-12-21 4:37 ` Daniel Palmer
2025-12-22 9:03 ` Kuan-Wei Chiu
2025-12-18 19:00 ` [PATCH 0/3] m68k: Add support for QEMU virt machine Tom Rini
2025-12-20 16:39 ` Kuan-Wei Chiu
2025-12-21 4:15 ` Daniel Palmer
2025-12-22 8:44 ` Kuan-Wei Chiu [this message]
2025-12-22 9:20 ` 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=aUkE-dvbDyZA_Ewy@google.com \
--to=visitorckw@gmail.com \
--cc=alison.wang@nxp.com \
--cc=angelo@kernel-space.org \
--cc=daniel@0x0f.com \
--cc=eleanor15x@gmail.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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