| commit | 43118f4351c1c430aa5c32aed80dcfe0b525a1f0 | |
| author | Peter Maydell <peter.maydell@linaro.org> | |
| Tue, 13 Mar 2018 15:34:51 +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 | 9e0b42fab21de07b66e6934850436f7462b3ddd6 | treesnapshot (tar.gz zip) |
| parent | 01e02f5aa74315f81b62872a50fe1b3e96dd00df | commitdiff |
hw/arm/boot: assert that secure_boot and secure_board_setup are false for AArch64
Add some assertions that if we're about to boot an AArch64 kernel,
the board code has not mistakenly set either secure_boot or
secure_board_setup. It doesn't make sense to set secure_boot,
because all AArch64 kernels must be booted in non-secure mode.
It might in theory make sense to set secure_board_setup, but
we don't currently support that, because only the AArch32
bootloader[] code calls this hook; bootloader_aarch64[] does not.
Since we don't have a current need for this functionality, just
assert that we don't try to use it. If it's needed we'll add
it later.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-id: 20180313153458.26822-3-peter.maydell@linaro.org
Add some assertions that if we're about to boot an AArch64 kernel,
the board code has not mistakenly set either secure_boot or
secure_board_setup. It doesn't make sense to set secure_boot,
because all AArch64 kernels must be booted in non-secure mode.
It might in theory make sense to set secure_board_setup, but
we don't currently support that, because only the AArch32
bootloader[] code calls this hook; bootloader_aarch64[] does not.
Since we don't have a current need for this functionality, just
assert that we don't try to use it. If it's needed we'll add
it later.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-id: 20180313153458.26822-3-peter.maydell@linaro.org
| hw/arm/boot.c | diffblobblamehistory |