qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: fanyihao@rt-thread.org
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v2 2/3] Add the STM32F4spark Machine
Date: Fri, 15 Aug 2025 18:52:19 +0100	[thread overview]
Message-ID: <CAFEAcA_BGuq5Eqwz6sX7STzsgY1jVOQ=hFyb6gQBvdT3vpTuQw@mail.gmail.com> (raw)
In-Reply-To: <20250721201134.13270-3-fanyihao@rt-thread.org>

On Mon, 21 Jul 2025 at 21:11, <fanyihao@rt-thread.org> wrote:
>
> From: Yihao Fan <fanyihao@rt-thread.org>
>
> Add the STM32F4spark machine model using the STM32F407 SoC.
>
> Signed-off-by: Yihao Fan <fanyihao@rt-thread.org>
> ---
>  MAINTAINERS           |  7 +++++++
>  hw/arm/Kconfig        |  6 ++++++
>  hw/arm/meson.build    |  1 +
>  hw/arm/stm32f4spark.c | 48 +++++++++++++++++++++++++++++++++++++++++++
>  4 files changed, 62 insertions(+)
>  create mode 100644 hw/arm/stm32f4spark.c
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 2744639a8b..0dc7c7bf60 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1030,6 +1030,13 @@ S: Maintained
>  F: hw/arm/stm32vldiscovery.c
>  F: docs/system/arm/stm32.rst
>
> +STM32F4SPARK
> +M: yanl1229 <yanl1229@rt-thread.org>
> +M: Yihao Fan <fanyihao@rt-thread.org>
> +L: qemu-arm@nongnu.org
> +S: Maintained
> +F: hw/arm/stm32f4spark.c
> +
>  Versatile Express
>  M: Peter Maydell <peter.maydell@linaro.org>
>  L: qemu-arm@nongnu.org
> diff --git a/hw/arm/Kconfig b/hw/arm/Kconfig
> index 4b2f71e6e1..3706a65286 100644
> --- a/hw/arm/Kconfig
> +++ b/hw/arm/Kconfig
> @@ -234,6 +234,12 @@ config STM32VLDISCOVERY
>      depends on TCG && ARM
>      select STM32F100_SOC
>
> +config STM32F4SPARK
> +    bool
> +    default y
> +    depends on TCG && ARM
> +    select STM32F407_SOC
> +
>  config STRONGARM
>      bool
>      select PXA2XX_TIMER
> diff --git a/hw/arm/meson.build b/hw/arm/meson.build
> index 31621060ba..ec63ed7373 100644
> --- a/hw/arm/meson.build
> +++ b/hw/arm/meson.build
> @@ -17,6 +17,7 @@ arm_common_ss.add(when: 'CONFIG_REALVIEW', if_true: files('realview.c'))
>  arm_ss.add(when: 'CONFIG_SBSA_REF', if_true: files('sbsa-ref.c'))
>  arm_common_ss.add(when: 'CONFIG_STELLARIS', if_true: files('stellaris.c'))
>  arm_common_ss.add(when: 'CONFIG_STM32VLDISCOVERY', if_true: files('stm32vldiscovery.c'))
> +arm_common_ss.add(when: 'CONFIG_STM32F4SPARK', if_true: files('stm32f4spark.c'))
>  arm_common_ss.add(when: 'CONFIG_ZYNQ', if_true: files('xilinx_zynq.c'))
>  arm_common_ss.add(when: 'CONFIG_SABRELITE', if_true: files('sabrelite.c'))
>
> diff --git a/hw/arm/stm32f4spark.c b/hw/arm/stm32f4spark.c
> new file mode 100644
> index 0000000000..e1d656a3f9
> --- /dev/null
> +++ b/hw/arm/stm32f4spark.c
> @@ -0,0 +1,48 @@
> +/* SPDX-License-Identifier: GPL-2.0-or-later */

Generally files should have something more than just the SPDX
tag in their opening comment. Usually that is a statement
of what the file contains. This is also a good place to put
a URL to the datasheet/reference manual/etc for the hardware
being modelled.

Otherwise this patch looks OK.

-- PMM


  reply	other threads:[~2025-08-15 17:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-21 20:11 [PATCH v2 0/3] Add STM32F4 support and USART device model fanyihao
2025-07-21 20:11 ` [PATCH v2 1/3] Add-the-stm32f407-SoC fanyihao
2025-08-15 17:56   ` Peter Maydell
2025-08-21 14:02     ` 范艺豪
2025-07-21 20:11 ` [PATCH v2 2/3] Add the STM32F4spark Machine fanyihao
2025-08-15 17:52   ` Peter Maydell [this message]
2025-08-21 14:04     ` 范艺豪
2025-07-21 20:11 ` [PATCH v2 3/3] Add STM32F4xx USART device model fanyihao
2025-08-15 17:46   ` Peter Maydell
2025-08-21 14:16     ` 范艺豪
2025-08-02  6:12 ` Re:[PATCH v2 0/3] Add STM32F4 support and " 范艺豪
2025-08-02 11:17   ` [PATCH " Peter Maydell
2025-08-04 15:31     ` fanyihao
2025-08-15 17:49 ` Peter Maydell
2025-08-21 13:45   ` 范艺豪

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='CAFEAcA_BGuq5Eqwz6sX7STzsgY1jVOQ=hFyb6gQBvdT3vpTuQw@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=fanyihao@rt-thread.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).