On 24/09/2018 15:09, Udit Kumar wrote:
Hi Grant
-----Original Message-----
From: [email protected] <arm.ebbr-discuss-
[email protected]> On Behalf Of Grant Likely
Sent: Monday, September 24, 2018 7:24 PM
To: [email protected]; [email protected]
Cc: [email protected]
Subject: [Arm.ebbr-discuss] [PATCH 1/7] Remove UEFI Loaded Image section
The UEFI spec already specifies the image format. No need to specify in EBBR.
Signed-off-by: Grant Likely <[email protected]>
---
source/chapter2-uefi.rst | 6 ------
1 file changed, 6 deletions(-)
diff --git a/source/chapter2-uefi.rst b/source/chapter2-uefi.rst index
177a81c..f89ac04 100644
--- a/source/chapter2-uefi.rst
+++ b/source/chapter2-uefi.rst
@@ -73,12 +73,6 @@ that virtual addresses must equal physical addresses.
The default RAM allocated attribute must be EFI_MEMORY_WB.
-UEFI Loaded Images
-------------------
-
-UEFI loaded images for AArch64 must be in 64-bit PE/COFF format and must -
contain only A64 code.
-
Configuration Tables
--------------------
Speaking about, u-boot image which is not PE/COFF format.
IMHO, document should provide this clarity.
This document only talks about UEFI interfaces. None of the U-Boot image
formats are mentioned at all. Section 2.1.1 covers UEFI image formats.
However, by loaded image we are referring to efi driver/application
which may run from u-boot shell, should have PE/COFF format
or I missed something on this section
Yes, the spec is entirely talking about EFI driver/application images. I
don't think EBBR needs to say anything at all about image formats, but
if you feel strongly about it I'll put it back in with more generic
language.
g.
_______________________________________________
boot-architecture mailing list
[email protected]
https://lists.linaro.org/mailman/listinfo/boot-architecture
