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:ASPEED BMCs" <qemu-arm@nongnu.org>,
"open list:All patches CC here" <qemu-devel@nongnu.org>
Cc: <troy_lee@aspeedtech.com>
Subject: Re: [PATCH v2 6/7] hw/arm/aspeed_ast27x0-fc: Map FMC0 flash contents into CA35 boot ROM
Date: Wed, 24 Sep 2025 12:17:50 +0200 [thread overview]
Message-ID: <eb5dc6d2-29d9-451e-9588-6a3de03a952e@kaod.org> (raw)
In-Reply-To: <20250924055602.294857-7-jamin_lin@aspeedtech.com>
On 9/24/25 07:56, Jamin Lin wrote:
> This patch introduces a dedicated ca35_boot_rom memory region and
> copies the FMC0 flash data into it when mmio_exec is disabled.
>
> The main purpose of this change is to support the upcoming VBOOTROM
> , which can directly fetch data from FMC0 flash at the SPI boot ROM
> base address (0x100000000) without requiring any SPI controller
> drivers.
That's the 'execute-in-place' case but the property activating
'execute-in-place' is always false in this machine. Could you
explain why booting from vbootrom needs the fmc0 contents to be
mapped in memory too ?
> Signed-off-by: Jamin Lin <jamin_lin@aspeedtech.com>
> ---
> hw/arm/aspeed_ast27x0-fc.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/hw/arm/aspeed_ast27x0-fc.c b/hw/arm/aspeed_ast27x0-fc.c
> index b15cb94c39..2e6036b192 100644
> --- a/hw/arm/aspeed_ast27x0-fc.c
> +++ b/hw/arm/aspeed_ast27x0-fc.c
> @@ -35,6 +35,7 @@ struct Ast2700FCState {
>
> MemoryRegion ca35_memory;
> MemoryRegion ca35_dram;
> + MemoryRegion ca35_boot_rom;
> MemoryRegion ssp_memory;
> MemoryRegion tsp_memory;
>
> @@ -61,7 +62,10 @@ static void ast2700fc_ca35_init(MachineState *machine)
> Ast2700FCState *s = AST2700A1FC(machine);
> AspeedSoCState *soc;
> AspeedSoCClass *sc;
> + BlockBackend *fmc0 = NULL;
> + DeviceState *dev = NULL;
> Error **errp = NULL;
> + uint64_t rom_size;
>
> object_initialize_child(OBJECT(s), "ca35", &s->ca35, "ast2700-a1");
> soc = ASPEED_SOC(&s->ca35);
> @@ -119,6 +123,16 @@ static void ast2700fc_ca35_init(MachineState *machine)
> ast2700fc_board_info.ram_size = machine->ram_size;
> ast2700fc_board_info.loader_start = sc->memmap[ASPEED_DEV_SDRAM];
>
> + if (!s->mmio_exec) {
bool 'mmio_exec' is always false in this machine. Should we keep it ?
Thanks,
C.
> + dev = ssi_get_cs(soc->fmc.spi, 0);
> + fmc0 = dev ? m25p80_get_blk(dev) : NULL;
> +
> + if (fmc0) {
> + rom_size = memory_region_size(&soc->spi_boot);
> + aspeed_install_boot_rom(soc, fmc0, &s->ca35_boot_rom, rom_size);
> + }
> + }
> +
> arm_load_kernel(ARM_CPU(first_cpu), machine, &ast2700fc_board_info);
> }
>
next prev parent reply other threads:[~2025-09-24 10:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 5:55 [PATCH v2 0/7] Support VBOOTROM to ast2700fc machine Jamin Lin via
2025-09-24 5:55 ` [PATCH v2 1/7] hw/arm/aspeed: Move aspeed_board_init_flashes() to common SoC code Jamin Lin via
2025-09-24 9:47 ` Cédric Le Goater
2025-09-24 5:55 ` [PATCH v2 2/7] hw/arm/aspeed: Move write_boot_rom " Jamin Lin via
2025-09-24 9:47 ` Cédric Le Goater
2025-09-24 5:55 ` [PATCH v2 3/7] hw/arm/aspeed: Move aspeed_install_boot_rom " Jamin Lin via
2025-09-24 9:47 ` Cédric Le Goater
2025-09-24 5:55 ` [PATCH v2 4/7] hw/arm/aspeed: Move aspeed_load_vbootrom " Jamin Lin via
2025-09-24 9:47 ` Cédric Le Goater
2025-09-24 5:55 ` [PATCH v2 5/7] hw/arm/aspeed_ast27x0-fc: Replace error_abort with local errp Jamin Lin via
2025-09-24 10:06 ` Cédric Le Goater
2025-09-25 2:13 ` Jamin Lin
2025-09-24 5:56 ` [PATCH v2 6/7] hw/arm/aspeed_ast27x0-fc: Map FMC0 flash contents into CA35 boot ROM Jamin Lin via
2025-09-24 10:17 ` Cédric Le Goater [this message]
2025-09-25 2:27 ` Jamin Lin
2025-09-24 5:56 ` [PATCH v2 7/7] hw/arm/aspeed_ast27x0-fc: Add VBOOTROM support Jamin Lin via
2025-09-24 10:18 ` 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=eb5dc6d2-29d9-451e-9588-6a3de03a952e@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=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).