| commit | 01e02f5aa74315f81b62872a50fe1b3e96dd00df | |
| author | Peter Maydell <peter.maydell@linaro.org> | |
| Tue, 13 Mar 2018 15:34:50 +0000 (13 15:34 +0000) | ||
| committer | Peter Maydell <peter.maydell@linaro.org> | |
| Mon, 19 Mar 2018 18:23:24 +0000 (19 18:23 +0000) | ||
| tree | 06214e062a075dc15d5a024f9b4a7f7e436f3971 | treesnapshot (tar.gz zip) |
| parent | 46d3fb634cb0e44c6cf0ed3a996d6996f3818c2d | commitdiff |
hw/arm/raspi: Don't do board-setup or secure-boot for raspi3
For the rpi1 and 2 we want to boot the Linux kernel via some
custom setup code that makes sure that the SMC instruction
acts as a no-op, because it's used for cache maintenance.
The rpi3 boots AArch64 kernels, which don't need SMC for
cache maintenance and always expect to be booted non-secure.
Don't fill in the aarch32-specific parts of the binfo struct.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Andrew Baumann <Andrew.Baumann@microsoft.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-id: 20180313153458.26822-2-peter.maydell@linaro.org
For the rpi1 and 2 we want to boot the Linux kernel via some
custom setup code that makes sure that the SMC instruction
acts as a no-op, because it's used for cache maintenance.
The rpi3 boots AArch64 kernels, which don't need SMC for
cache maintenance and always expect to be booted non-secure.
Don't fill in the aarch32-specific parts of the binfo struct.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Andrew Baumann <Andrew.Baumann@microsoft.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-id: 20180313153458.26822-2-peter.maydell@linaro.org
| hw/arm/raspi.c | diffblobblamehistory |