From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Jamin Lin" <jamin_lin@aspeedtech.com>,
"Cédric Le Goater" <clg@kaod.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"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 v0 2/2] aspeed: fix hardcode boot address 0
Date: Mon, 5 Feb 2024 14:20:25 +0100 [thread overview]
Message-ID: <46d14718-2b2c-45aa-aa12-854a2704383b@linaro.org> (raw)
In-Reply-To: <20240205091415.935686-3-jamin_lin@aspeedtech.com>
Hi Jamin,
On 5/2/24 10:14, Jamin Lin via wrote:
> In the previous design of QEMU model for ASPEED SOCs, it set the boot
> address at 0 which was the hardcode setting for ast10x0, ast2600,
> ast2500 and ast2400.
>
> According to the design of ast2700, it has bootmcu which is used for
> executing SPL and initialize DRAM,
Out of curiosity, what architecture is this MCU?
> then, CPUs(cortex-a35)
> execute u-boot, kernel and rofs. QEMU will only support CPU(coretax-a35)
> parts and the boot address is "0x400000000" for ast2700.
OK, but I don't get how you get from here ...
> Therefore, fixed hardcode boot address 0.
... to here.
> Signed-off-by: Troy Lee <troy_lee@aspeedtech.com>
> Signed-off-by: Jamin Lin <jamin_lin@aspeedtech.com>
> ---
> hw/arm/aspeed.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/hw/arm/aspeed.c b/hw/arm/aspeed.c
> index 218b81298e..82a92e8142 100644
> --- a/hw/arm/aspeed.c
> +++ b/hw/arm/aspeed.c
> @@ -289,12 +289,14 @@ static void aspeed_install_boot_rom(AspeedMachineState *bmc, BlockBackend *blk,
> uint64_t rom_size)
> {
> AspeedSoCState *soc = bmc->soc;
> + AspeedSoCClass *sc = ASPEED_SOC_GET_CLASS(soc);
>
> memory_region_init_rom(&bmc->boot_rom, NULL, "aspeed.boot_rom", rom_size,
> &error_abort);
> memory_region_add_subregion_overlap(&soc->spi_boot_container, 0,
> &bmc->boot_rom, 1);
> - write_boot_rom(blk, ASPEED_SOC_SPI_BOOT_ADDR, rom_size, &error_abort);
> + write_boot_rom(blk, sc->memmap[ASPEED_DEV_SPI_BOOT],
> + rom_size, &error_abort);
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> }
>
> void aspeed_board_init_flashes(AspeedSMCState *s, const char *flashtype,
next prev parent reply other threads:[~2024-02-05 13:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 9:14 [v0 0/2] uart base and hardcode boot address 0 Jamin Lin via
2024-02-05 9:14 ` [PATCH v0 1/2] aspeed: support uart controller both 0 and 1 base Jamin Lin via
2024-02-05 10:46 ` Cédric Le Goater
2024-02-05 13:15 ` Philippe Mathieu-Daudé
2024-02-06 3:08 ` Jamin Lin
2024-02-06 16:46 ` Cédric Le Goater
2024-02-05 14:25 ` Cédric Le Goater
2024-02-06 3:29 ` Jamin Lin
2024-02-06 16:59 ` Cédric Le Goater
2024-02-07 3:43 ` Jamin Lin
2024-02-06 17:36 ` Cédric Le Goater
2024-02-05 9:14 ` [PATCH v0 2/2] aspeed: fix hardcode boot address 0 Jamin Lin via
2024-02-05 13:20 ` Philippe Mathieu-Daudé [this message]
2024-02-06 1:48 ` Jamin Lin
2024-02-06 16:54 ` Cédric Le Goater
2024-02-05 13:34 ` Cédric Le Goater
2024-02-06 2:15 ` Jamin Lin
2024-02-06 16:47 ` [v0 0/2] uart base and " Cédric Le Goater
2024-02-07 3:41 ` Jamin Lin
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=46d14718-2b2c-45aa-aa12-854a2704383b@linaro.org \
--to=philmd@linaro.org \
--cc=andrew@codeconstruct.com.au \
--cc=clg@kaod.org \
--cc=jamin_lin@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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).