On Fri, 4 Sept 2026 at 17:02, Vincent Stehlé <[email protected]> wrote: > > U-Boot can support multiple EBBR conformance profiles, and it can advertise > them in the ECPT; therefore, remove the EBBR fixed version 2.1 mention from > the documentation and add a word about the ECPT profiles. > > While at it, fix one typo. > > Signed-off-by: Vincent Stehlé <[email protected]> > Cc: Heinrich Schuchardt <[email protected]> > Cc: Ilias Apalodimas <[email protected]> > Cc: Tom Rini <[email protected]> > ---
Acked-by: Ilias Apalodimas <[email protected]> > doc/develop/uefi/uefi.rst | 18 +++++++++++++----- > 1 file changed, 13 insertions(+), 5 deletions(-) > > diff --git a/doc/develop/uefi/uefi.rst b/doc/develop/uefi/uefi.rst > index 94ddf690440..9dc34495f66 100644 > --- a/doc/develop/uefi/uefi.rst > +++ b/doc/develop/uefi/uefi.rst > @@ -14,14 +14,23 @@ Development target > ------------------ > > The implementation of UEFI in U-Boot strives to reach the requirements > described > -in the "Embedded Base Boot Requirements (EBBR) Specification - Release > v2.1.0" > -[2]. The "Server Base Boot Requirements System Software on ARM Platforms" [3] > +in the "Embedded Base Boot Requirements (EBBR) Specification" [2]. > +The "Server Base Boot Requirements System Software on ARM Platforms" [3] > describes a superset of the EBBR specification and may be used as further > reference. > > A full blown UEFI implementation would contradict the U-Boot design principle > "keep it small". > > +Conformance profiles > +~~~~~~~~~~~~~~~~~~~~ > + > +The EBBR conformance profiles supported by U-Boot are inferred optimistically > +from its configuration and the corresponding GUIDs are advertised in the EFI > +Conformance Profiles Table (ECPT) automatically by default. > +System integrators should review the advertised profiles and override > manually > +if necessary. > + > Building U-Boot for UEFI > ------------------------ > > @@ -323,7 +332,7 @@ Capsule with firmware version > > The UEFI specification does not define the firmware versioning mechanism. > EDK II reference implementation inserts the FMP Payload Header right before > -the payload. It coutains the fw_version and lowest supported version, > +the payload. It contains the fw_version and lowest supported version, > EDK II reference implementation uses these information to implement the > firmware versioning and anti-rollback protection, the firmware version and > lowest supported version is stored into EFI non-volatile variable. > @@ -1019,8 +1028,7 @@ Links > ----- > > * [1] http://uefi.org/specifications - UEFI specifications > -* [2] > https://github.com/ARM-software/ebbr/releases/download/v2.1.0/ebbr-v2.1.0.pdf > - > - Embedded Base Boot Requirements (EBBR) Specification - Release v2.1.0 > +* [2] https://github.com/ARM-software/ebbr - Embedded Base Boot Requirements > (EBBR) Specification > * [3] > https://developer.arm.com/docs/den0044/latest/server-base-boot-requirements-system-software-on-arm-platforms-version-11 > - > Server Base Boot Requirements System Software on ARM Platforms - Version > 1.1 > * [4] :doc:`iscsi` > > -- > 2.53.0 >
