On 28.03.19 14:11, Heinrich Schuchardt wrote:
Describe the target scope of the UEFI implementation in U-Boot.
Signed-off-by: Heinrich Schuchardt xypron.glpk@gmx.de
doc/README.uefi | 11 +++++++++++ 1 file changed, 11 insertions(+)
diff --git a/doc/README.uefi b/doc/README.uefi index b38efbc0cc..66b6abece5 100644 --- a/doc/README.uefi +++ b/doc/README.uefi @@ -12,6 +12,15 @@ the interaction of drivers and applications with the firmware. The API comprises access to block storage, network, and console to name a few. The Linux kernel and boot loaders like GRUB or the FreeBSD loader can be executed.
+## Development target
+The implementation of UEFI in U-Boot strives to reach the minimum requirements +described in "Server Base Boot Requirements System Software on ARM Platforms - +Version 1.1" [4].
+A full blown UEFI implementation would contradict the U-Boot design principle +"keep it small".
I'm not sure we ever want to be fully SBBR compliant. We might be, but it's not been a goal so far. We do however want to be *EBBR* compliant.
Alex
## Building for UEFI
The UEFI standard supports only little-endian systems. The UEFI support can be @@ -335,3 +344,5 @@ This driver is only available if U-Boot is configured with http://uefi.org/specifications - UEFI specifications
- [2](./driver-model/README.txt) doc/driver-model/README.txt - Driver model
- [3](./README.iscsi) doc/README.iscsi - iSCSI booting with U-Boot and iPXE
+* [4](https://developer.arm.com/docs/den0044/latest/server-base-boot-requirements-...)
- Server Base Boot Requirements System Software on ARM Platforms - Version 1.1
-- 2.20.1