diff options
| author | Jamin Lin <jamin_lin@aspeedtech.com> | 2025-03-04 14:47:08 +0800 |
|---|---|---|
| committer | Cédric Le Goater <clg@redhat.com> | 2025-03-09 14:36:53 +0100 |
| commit | 8dd163f915cf26277fa175476c0af6898b8fd864 (patch) | |
| tree | 9fd5a85e03145949c8ef0f5ec4cdf8a8d2d47556 /docs/sphinx/compat.py | |
| parent | b741ab395b398058198ba3f055d9d8c4d631122f (diff) | |
| download | qemu-8dd163f915cf26277fa175476c0af6898b8fd864.zip qemu-8dd163f915cf26277fa175476c0af6898b8fd864.tar.gz qemu-8dd163f915cf26277fa175476c0af6898b8fd864.tar.bz2 | |
hw/arm/aspeed_ast27x0.c Fix boot issue for AST2700
Currently, ASPEED_DEV_SPI_BOOT is set to "0x400000000", which is the DRAM start
address, and the QEMU loader is used to load the U-Boot binary into this address.
However, if users want to install FMC flash contents as a boot ROM, the DRAM
address 0x400000000 would be overwritten with Boot ROM data. This causes the
AST2700 to fail to boot because the U-Boot data becomes incorrect.
To fix this, change the ASPEED_DEV_SPI_BOOT address to "0x100000000", which is
the FMC0 memory-mapped start address in the AST2700.
Signed-off-by: Jamin Lin <jamin_lin@aspeedtech.com>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Tested-by: Nabih Estefan <nabihestefan@google.com>
Link: https://lore.kernel.org/qemu-devel/20250304064710.2128993-7-jamin_lin@aspeedtech.com
Signed-off-by: Cédric Le Goater <clg@redhat.com>
Diffstat (limited to 'docs/sphinx/compat.py')
0 files changed, 0 insertions, 0 deletions