From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Jackson Donaldson <jackson88044@gmail.com>,
qemu-arm <qemu-arm@nongnu.org>,
Jackson Donaldson <jcksn@duck.com>
Subject: Re: [PULL 01/36] MAX78000: Add MAX78000FTHR Machine
Date: Mon, 29 Sep 2025 08:57:14 +0200 [thread overview]
Message-ID: <008fd065-6332-470c-9ff0-1bccb026ea69@redhat.com> (raw)
In-Reply-To: <20250711133429.1423030-2-peter.maydell@linaro.org>
On 11/07/2025 15.33, Peter Maydell wrote:
> From: Jackson Donaldson <jackson88044@gmail.com>
>
> This patch adds support for the MAX78000FTHR machine.
>
> The MAX78000FTHR contains a MAX78000 and a RISC-V core. This patch
> implements only the MAX78000, which is Cortex-M4 based.
> Details can be found at:
> https://www.analog.com/media/en/technical-documentation/user-guides/max78000-user-guide.pdf
>
> Signed-off-by: Jackson Donaldson <jcksn@duck.com>
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
> Message-id: 20250704223239.248781-2-jcksn@duck.com
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> include/hw/arm/max78000_soc.h | 35 +++++++
> hw/arm/max78000_soc.c | 172 ++++++++++++++++++++++++++++++++++
> hw/arm/max78000fthr.c | 50 ++++++++++
> hw/arm/Kconfig | 10 ++
> hw/arm/meson.build | 2 +
> 5 files changed, 269 insertions(+)
> create mode 100644 include/hw/arm/max78000_soc.h
> create mode 100644 hw/arm/max78000_soc.c
> create mode 100644 hw/arm/max78000fthr.c
Hi Peter, hi Jackson,
could you please also provide a patch that adds an entry for this machine in
the MAINTAINERS file? (I just noticed that
tests/functional/arm/test_max78000fthr.py does not have any maintainer,
that's why I'm asking)
Thanks,
Thomas
next prev parent reply other threads:[~2025-09-29 6:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 13:33 [PULL 00/36] target-arm queue Peter Maydell
2025-07-11 13:33 ` [PULL 01/36] MAX78000: Add MAX78000FTHR Machine Peter Maydell
2025-09-29 6:57 ` Thomas Huth [this message]
2025-10-07 2:33 ` Philippe Mathieu-Daudé
2025-07-11 13:33 ` [PULL 02/36] MAX78000: ICC Implementation Peter Maydell
2025-07-11 13:33 ` [PULL 03/36] MAX78000: Add ICC to SOC Peter Maydell
2025-07-11 13:33 ` [PULL 04/36] MAX78000: UART Implementation Peter Maydell
2025-07-11 13:33 ` [PULL 05/36] MAX78000: Add UART to SOC Peter Maydell
2025-07-11 13:33 ` [PULL 06/36] MAX78000: GCR Implementation Peter Maydell
2025-07-11 13:34 ` [PULL 07/36] MAX78000: Add GCR to SOC Peter Maydell
2025-07-11 13:34 ` [PULL 08/36] MAX78000: TRNG Implementation Peter Maydell
2025-07-11 13:34 ` [PULL 09/36] MAX78000: Add TRNG to SOC Peter Maydell
2025-07-11 13:34 ` [PULL 10/36] MAX78000: AES implementation Peter Maydell
2025-07-11 13:34 ` [PULL 11/36] MAX78000: Add AES to SOC Peter Maydell
2025-07-11 13:34 ` [PULL 12/36] hw/cxl-host: Add an index field to CXLFixedMemoryWindow Peter Maydell
2025-07-11 13:34 ` [PULL 13/36] hw/cxl: Make the CXL fixed memory windows devices Peter Maydell
2025-07-11 13:34 ` [PULL 14/36] hw/arm/virt: Basic CXL enablement on pci_expander_bridge instances pxb-cxl Peter Maydell
2025-07-11 13:34 ` [PULL 15/36] docs/cxl: Add an arm/virt example Peter Maydell
2025-07-11 13:34 ` [PULL 16/36] qtest/cxl: Add aarch64 virt test for CXL Peter Maydell
2025-07-11 13:34 ` [PULL 17/36] arm/cpu: store id_afr0 into the idregs array Peter Maydell
2025-07-11 13:34 ` [PULL 18/36] arm/cpu: store id_aa64afr{0,1} " Peter Maydell
2025-07-11 13:34 ` [PULL 19/36] arm/cpu: fix trailing ',' for SET_IDREG Peter Maydell
2025-07-11 13:34 ` [PULL 20/36] arm/cpu: store clidr into the idregs array Peter Maydell
2025-07-11 13:34 ` [PULL 21/36] arm/kvm: shorten one overly long line Peter Maydell
2025-07-11 13:34 ` [PULL 22/36] target/arm: Drop stub for define_tlb_insn_regs Peter Maydell
2025-07-11 13:34 ` [PULL 23/36] target/arm: Split out AT insns to tcg/cpregs-at.c Peter Maydell
2025-07-11 13:34 ` [PULL 24/36] target/arm: Split out performance monitor regs to cpregs-pmu.c Peter Maydell
2025-07-11 13:34 ` [PULL 25/36] target/arm: Don't enforce NSE, NS check for EL3->EL3 returns Peter Maydell
2025-07-11 13:34 ` [PULL 26/36] hw/arm/fsl-imx8mp: Wire VIRQ and VFIQ Peter Maydell
2025-07-11 13:34 ` [PULL 27/36] hw/arm: Allow setting KVM vGIC maintenance IRQ Peter Maydell
2025-07-11 13:34 ` [PULL 28/36] target/arm/kvm: Add helper to detect EL2 when using KVM Peter Maydell
2025-07-11 13:34 ` [PULL 29/36] target/arm: Enable feature ARM_FEATURE_EL2 if EL2 is supported Peter Maydell
2025-07-11 13:34 ` [PULL 30/36] hw/arm/arm_gicv3_kvm: Add a migration blocker with kvm nested virt Peter Maydell
2025-07-11 13:34 ` [PULL 31/36] hw/arm/virt: Allow virt extensions with KVM Peter Maydell
2025-07-11 13:34 ` [PULL 32/36] system/qdev: Remove pointless NULL check in qdev_device_add_from_qdict Peter Maydell
2025-07-11 13:34 ` [PULL 33/36] hw/arm/virt-acpi-build: Don't create ITS id mappings by default Peter Maydell
2025-07-11 13:34 ` [PULL 34/36] target/arm: Remove helper_sme2_luti4_4b Peter Maydell
2025-07-11 13:34 ` [PULL 35/36] docs/system: arm: Add max78000 board description Peter Maydell
2025-07-11 13:34 ` [PULL 36/36] tests/functional: Add a test for the MAX78000 arm machine Peter Maydell
2025-07-13 7:06 ` [PULL 00/36] target-arm queue Stefan Hajnoczi
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=008fd065-6332-470c-9ff0-1bccb026ea69@redhat.com \
--to=thuth@redhat.com \
--cc=jackson88044@gmail.com \
--cc=jcksn@duck.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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).