summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/imx28-cfa10057.dts
diff options
context:
space:
mode:
authorArd Biesheuvel <ardb@kernel.org>2022-09-22 13:03:52 +0300
committerArd Biesheuvel <ardb@kernel.org>2022-09-27 14:26:16 +0300
commit3c6edd9034240ce9582be3392112321336bd25bb (patch)
tree0f0aabffc23d2eed052440071db2fbc8e1a7fc34 /arch/arm/boot/dts/imx28-cfa10057.dts
parent04419e8a7b41c83c628d45c684d6bd117c24cea9 (diff)
downloadlinux-3c6edd9034240ce9582be3392112321336bd25bb.tar.xz
efi: zboot: create MemoryMapped() device path for the parent if needed
LoadImage() is supposed to install an instance of the protocol EFI_LOADED_IMAGE_DEVICE_PATH_PROTOCOL onto the loaded image's handle so that the program can figure out where it was loaded from. The reference implementation even does this (with a NULL protocol pointer) if the call to LoadImage() used the source buffer and size arguments, and passed NULL for the image device path. Hand rolled implementations of LoadImage may behave differently, though, and so it is better to tolerate situations where the protocol is missing. And actually, concatenating an Offset() node to a NULL device path (as we do currently) is not great either. So in cases where the protocol is absent, or when it points to NULL, construct a MemoryMapped() device node as the base node that describes the parent image's footprint in memory. Cc: Daan De Meyer <daandemeyer@fb.com> Cc: Jeremy Linton <jeremy.linton@arm.com> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'arch/arm/boot/dts/imx28-cfa10057.dts')
0 files changed, 0 insertions, 0 deletions