summaryrefslogtreecommitdiffstats
path: root/Documentation/pcmcia
diff options
context:
space:
mode:
authorSameer Goel <sgoel@codeaurora.org>2017-04-03 11:26:33 +0900
committerCatalin Marinas <catalin.marinas@arm.com>2017-04-05 18:32:47 +0100
commitae8a442dfdc4fc3197c8aa09bb179345b2c1f49e (patch)
tree162a2253bc2024f4bdf28ca1e1b359ba400bdd48 /Documentation/pcmcia
parentfcbd4bb71e913d4be7a6d39f622479499bb73bfe (diff)
downloadop-kernel-dev-ae8a442dfdc4fc3197c8aa09bb179345b2c1f49e.zip
op-kernel-dev-ae8a442dfdc4fc3197c8aa09bb179345b2c1f49e.tar.gz
efi/libstub/arm*: Set default address and size cells values for an empty dtb
In cases where a device tree is not provided (ie ACPI based system), an empty fdt is generated by efistub. #address-cells and #size-cells are not set in the empty fdt, so they default to 1 (4 byte wide). This can be an issue on 64-bit systems where values representing addresses, etc may be 8 bytes wide as the default value does not align with the general requirements for an empty DTB, and is fragile when passed to other agents as extra care is required to read the entire width of a value. This issue is observed on Qualcomm Technologies QDF24XX platforms when kexec-tools inserts 64-bit addresses into the "linux,elfcorehdr" and "linux,usable-memory-range" properties of the fdt. When the values are later consumed, they are truncated to 32-bit. Setting #address-cells and #size-cells to 2 at creation of the empty fdt resolves the observed issue, and makes the fdt less fragile. Signed-off-by: Sameer Goel <sgoel@codeaurora.org> Signed-off-by: Jeffrey Hugo <jhugo@codeaurora.org> Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'Documentation/pcmcia')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud