Skip to contentSkip to conversation

efi/zboot: Fix outdated comment about using LoadImage/StartImage

PATCH New Ard Biesheuvel 1 participant 1 message Nov 15, 2024 EFI

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 efi/zboot: Fix outdated comment about using LoadImage/StartImage

From: Ard Biesheuvel <[email protected]>

EFI zboot no longer uses LoadImage/StartImage, but subsumes the arch code to load and start the bare metal image directly. Fix the Kconfig description accordingly.

---
 drivers/firmware/efi/Kconfig | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)
drivers/firmware/efi/Kconfig +4 -6
index 72f2537d90ca..e312d731f4a3 100644
@@ -84,12 +84,10 @@ config EFI_ZBOOT
 	help
 	  Create the bootable image as an EFI application that carries the
 	  actual kernel image in compressed form, and decompresses it into
-	  memory before executing it via LoadImage/StartImage EFI boot service
-	  calls. For compatibility with non-EFI loaders, the payload can be
-	  decompressed and executed by the loader as well, provided that the
-	  loader implements the decompression algorithm and that non-EFI boot
-	  is supported by the encapsulated image. (The compression algorithm
-	  used is described in the zboot image header)
+	  memory before executing it. For compatibility with non-EFI loaders,
+	  the payload can be decompressed and executed by the loader as well,
+	  provided that the loader implements the decompression algorithm.
+	  (The compression algorithm used is described in the zboot header)
 
 config EFI_ARMSTUB_DTB_LOADER
 	bool "Enable the DTB loader"
Signature · 1 line
2.47.0.338.g60cca15819-goog