Hi,
Just a gentle ping on this patch series:
  [PATCH v2 0/3] Add STM32F4 support and USART device model
https://patchew.org/QEMU/[email protected]/



This patch adds support for the STM32F407 SoC, a new STM32F4spark board,
and a USART device model. Feedback would be greatly appreciated.



This patch will be applied in the /hw/arm directory.



Let me know if any changes are needed or if I should rebase it on a newer tree.
Best regards,
 Yihao Fan
[email protected]











Original:
From:Yihao Fan <[email protected]>Date:2025-07-22 04:11:31(中国 
(GMT+08:00))To:qemu-devel<[email protected]>Cc:Peter Maydell 
<[email protected]> , Yihao Fan <[email protected]>Subject:[PATCH 
v2 0/3] Add STM32F4 support and USART device modelFrom: Yihao Fan 
<[email protected]>

This patch series introduces basic support for the STM32F407 SoC and
a new STM32F4spark machine in QEMU, along with a USART device model.

This series includes:
- A new SoC model (STM32F407) with initial integration.
- A board model called STM32F4spark to instantiate and test the SoC.
- A USART device implementation for STM32F4xx family.

Signed-off-by: Yihao Fan <[email protected]>

Yihao Fan (3):
  Add-the-stm32f407-SoC
  Add the STM32F4spark Machine
  Add STM32F4xx USART device model

 MAINTAINERS                       |  16 ++
 hw/arm/Kconfig                    |  13 ++
 hw/arm/meson.build                |   2 +
 hw/arm/stm32f407_soc.c            | 154 +++++++++++++++++++
 hw/arm/stm32f4spark.c             |  48 ++++++
 hw/char/Kconfig                   |   3 +
 hw/char/meson.build               |   1 +
 hw/char/stm32f4xx_usart.c         | 236 ++++++++++++++++++++++++++++++
 include/hw/arm/stm32f407_soc.h    |  47 ++++++
 include/hw/char/stm32f4xx_usart.h |  60 ++++++++
 10 files changed, 580 insertions(+)
 create mode 100644 hw/arm/stm32f407_soc.c
 create mode 100644 hw/arm/stm32f4spark.c
 create mode 100644 hw/char/stm32f4xx_usart.c
 create mode 100644 include/hw/arm/stm32f407_soc.h
 create mode 100644 include/hw/char/stm32f4xx_usart.h

-- 
2.43.0







Reply via email to