efi/libstub: arm32: Base FDT and initrd placement on image address
authorArd Biesheuvel <ardb@kernel.org>
Thu, 10 Sep 2020 14:09:45 +0000 (17:09 +0300)
committerArd Biesheuvel <ardb@kernel.org>
Wed, 16 Sep 2020 15:53:42 +0000 (18:53 +0300)
commit6208857b8f7ebdfe84e1be7573be4552a5896a0d
tree39ed3fecefb71f74bc9b30e3fa2eac17cf1ca115
parentf30f242fb1319e616fbcf94a43195a1c57db99b8
efi/libstub: arm32: Base FDT and initrd placement on image address

The way we use the base of DRAM in the EFI stub is problematic as it
is ill defined what the base of DRAM actually means. There are some
restrictions on the placement of FDT and initrd which are defined in
terms of dram_base, but given that the placement of the kernel in
memory is what defines these boundaries (as on ARM, this is where the
linear region starts), it is better to use the image address in these
cases, and disregard dram_base altogether.

Reviewed-by: Maxim Uvarov <maxim.uvarov@linaro.org>
Tested-by: Maxim Uvarov <maxim.uvarov@linaro.org>
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
arch/arm/include/asm/efi.h
arch/arm64/include/asm/efi.h
drivers/firmware/efi/libstub/arm32-stub.c
drivers/firmware/efi/libstub/efi-stub.c