summaryrefslogtreecommitdiff
path: root/boot
diff options
context:
space:
mode:
authorSimon Glass <[email protected]>2023-12-15 16:54:16 -0700
committerTom Rini <[email protected]>2024-01-11 21:19:25 -0500
commit99abd60d59e277f1b0853dfd6d4fdf6e8014ab30 (patch)
tree317ebfda72abcc59f311d5ef645f62b414d3865c /boot
parent4f6dd2580042dbdc28fcd4f369ff18c089adaca9 (diff)
boot: Support decompressing non-kernel OS images
Sometimes the kernel is built as an EFI application rather than a binary. We still want to support compression for this case. For arm64 the entry point is set later in the bootm_load_os() function, since these images are typically relocated due to the 2MB-alignment requirement of arm64 images. But since the EFI image is not in the same format, we need to update the entry point earlier. Set the entry point always, for kernel_noload to resolve this problem. It should be harmless to do this always. Signed-off-by: Simon Glass <[email protected]>
Diffstat (limited to 'boot')
-rw-r--r--boot/bootm.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/boot/bootm.c b/boot/bootm.c
index 7a050ed41a7..d071537d692 100644
--- a/boot/bootm.c
+++ b/boot/bootm.c
@@ -644,6 +644,7 @@ static int bootm_load_os(struct bootm_headers *images, int boot_progress)
if (!load)
return 1;
os.load = load;
+ images->ep = load;
debug("Allocated %lx bytes at %lx for kernel (size %lx) decompression\n",
req_size, load, image_len);
}