qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: Jamin Lin <jamin_lin@aspeedtech.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Steven Lee <steven_lee@aspeedtech.com>,
	Troy Lee <leetroy@gmail.com>,
	Andrew Jeffery <andrew@codeconstruct.com.au>,
	Joel Stanley <joel@jms.id.au>,
	"open list:All patches CC here" <qemu-devel@nongnu.org>,
	"open list:ASPEED BMCs" <qemu-arm@nongnu.org>
Cc: troy_lee@aspeedtech.com, nabihestefan@google.com
Subject: Re: [PATCH v2 00/10] Support vbootrom for AST2700
Date: Fri, 11 Apr 2025 17:48:23 +0200	[thread overview]
Message-ID: <d44e6583-c9af-4216-b715-aa4aa8968048@kaod.org> (raw)
In-Reply-To: <20250410023856.500258-1-jamin_lin@aspeedtech.com>

Hello Jamin

On 4/10/25 04:38, Jamin Lin wrote:
> v1:
>    Add initial support for AST27x0
>    The purpose of vbootrom here is to simulate the work of BootMCU SPL (riscv)
>    in AST2700, because QEMU doesn't support heterogenous architecture yet.
> 
>    ast27x0_bootrom.bin is a simplified, free (Apache 2.0) boot ROM for
>    ASPEED AST27x0 BMC SOC. It currently implements the bare minimum to
>    load, parse, initialize and run boot images stored in SPI flash, but may grow
>    more features over time as needed. The source code is available at:
>    https://github.com/google/vbootrom

I don't see any updates on the vbootrom github repo for Aspeed SoCs. Is the
vbootrom compatible with the Nuvoton SoC ?


Thanks,

C.




> v2:
>    Add "Introduced ASPEED_DEV_VBOOTROM in the device enumeration" patch to fix
>    build failed.
> 
> Jamin Lin (10):
>    hw/arm/aspeed: Introduced ASPEED_DEV_VBOOTROM in the device
>      enumeration
>    hw/arm/aspeed_ast27x0: Add "vbootrom_size" field to AspeedSoCClass
>    hw/arm/aspeed_ast27x0: Rename variable sram_name to name in ast2700
>      realize
>    hw/arm/aspeed_ast27x0 Introduce vbootrom memory region
>    hw/arm/aspeed: Enable vbootrom support by default on AST2700 EVB
>      machines
>    hw/arm/aspeed: Reuse rom_size variable for vbootrom setup
>    hw/arm/aspeed: Add support for loading vbootrom image via "-bios"
>    pc-bios: Add AST27x0 vBootrom
>    tests/functional/aspeed: Update AST2700 functional test to use
>      vbootrom
>    docs/system/arm/aspeed: Support vbootrom for AST2700
> 
>   MAINTAINERS                             |   1 +
>   docs/system/arm/aspeed.rst              |  18 +++--------
>   include/hw/arm/aspeed.h                 |   1 +
>   include/hw/arm/aspeed_soc.h             |   3 ++
>   hw/arm/aspeed.c                         |  37 ++++++++++++++++++++++-
>   hw/arm/aspeed_ast27x0.c                 |  20 ++++++++++---
>   pc-bios/README                          |   6 ++++
>   pc-bios/ast27x0_bootrom.bin             | Bin 0 -> 15464 bytes
>   pc-bios/meson.build                     |   1 +
>   tests/functional/test_aarch64_aspeed.py |  38 +-----------------------
>   10 files changed, 69 insertions(+), 56 deletions(-)
>   create mode 100644 pc-bios/ast27x0_bootrom.bin
> 



  parent reply	other threads:[~2025-04-11 15:49 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10  2:38 [PATCH v2 00/10] Support vbootrom for AST2700 Jamin Lin via
2025-04-10  2:38 ` [PATCH v2 01/10] hw/arm/aspeed: Introduced ASPEED_DEV_VBOOTROM in the device enumeration Jamin Lin via
2025-04-10  2:38 ` [PATCH v2 02/10] hw/arm/aspeed_ast27x0: Add "vbootrom_size" field to AspeedSoCClass Jamin Lin via
2025-04-10  2:38 ` [PATCH v2 03/10] hw/arm/aspeed_ast27x0: Rename variable sram_name to name in ast2700 realize Jamin Lin via
2025-04-11 15:48   ` Cédric Le Goater
2025-04-10  2:38 ` [PATCH v2 04/10] hw/arm/aspeed_ast27x0 Introduce vbootrom memory region Jamin Lin via
2025-04-11 15:50   ` Cédric Le Goater
2025-04-14  1:22     ` Jamin Lin
2025-04-10  2:38 ` [PATCH v2 05/10] hw/arm/aspeed: Enable vbootrom support by default on AST2700 EVB machines Jamin Lin via
2025-04-10  2:38 ` [PATCH v2 06/10] hw/arm/aspeed: Reuse rom_size variable for vbootrom setup Jamin Lin via
2025-04-11 15:50   ` Cédric Le Goater
2025-04-10  2:38 ` [PATCH v2 07/10] hw/arm/aspeed: Add support for loading vbootrom image via "-bios" Jamin Lin via
2025-04-11 16:07   ` Cédric Le Goater
2025-04-14  3:17     ` Jamin Lin
2025-04-14 21:14       ` Nabih Estefan
2025-04-15  9:34         ` Jamin Lin
2025-04-15 16:07           ` Nabih Estefan
2025-04-16  2:21             ` Jamin Lin
2025-04-10  2:38 ` [PATCH v2 08/10] pc-bios: Add AST27x0 vBootrom Jamin Lin via
2025-04-11 15:58   ` Cédric Le Goater
2025-04-14  6:50     ` Jamin Lin
2025-04-21 16:31       ` Cédric Le Goater
2025-04-10  2:38 ` [PATCH v2 09/10] tests/functional/aspeed: Update AST2700 functional test to use vbootrom Jamin Lin via
2025-04-11 15:54   ` Cédric Le Goater
2025-04-14  2:06     ` Jamin Lin
2025-04-10  2:38 ` [PATCH v2 10/10] docs/system/arm/aspeed: Support vbootrom for AST2700 Jamin Lin via
2025-04-11 15:48 ` Cédric Le Goater [this message]
2025-04-14  1:20   ` [PATCH v2 00/10] " Jamin Lin
2025-04-21 16:08     ` Cédric Le Goater

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=d44e6583-c9af-4216-b715-aa4aa8968048@kaod.org \
    --to=clg@kaod.org \
    --cc=andrew@codeconstruct.com.au \
    --cc=jamin_lin@aspeedtech.com \
    --cc=joel@jms.id.au \
    --cc=leetroy@gmail.com \
    --cc=nabihestefan@google.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=steven_lee@aspeedtech.com \
    --cc=troy_lee@aspeedtech.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 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).