u-boot.git/lib/efi_loader/Makefile, branch master

efi_vars: Implement SPI Flash store

2026-03-14T07:15:09+00:00

Currently U-Boot uses ESP as storage for EFI variables.
Devices with SPI Flash are used for storing environment with this
commit we allow EFI variables to be stored on SPI Flash.

Signed-off-by: Shantur Rathore 
Signed-off-by: Michal Simek 
Tested-by: Neil Armstrong  # on AML-S905D3-CC
Acked-by: Ilias Apalodimas

efi_var_file: refactor to move buffer functions

2026-02-15T08:14:31+00:00

Currently efi_var_file.c has functions to store/read
EFI variables to/from memory buffer. These functions
can be used with other EFI variable stores so move
them out to efi_var_common.c

Signed-off-by: Shantur Rathore 
Signed-off-by: Michal Simek 
Tested-by: Neil Armstrong  # on AML-S905D3-CC
Reviewed-by: Ilias Apalodimas 
Reviewed-by: Heinrich Schuchardt

kbuild: Bump the build system to 6.1

2026-01-02T16:28:14+00:00

Our last sync with the kernel was 5.1.

We are so out of sync now, that tracking the patches and backporting
them one by one makes little sense and it's going to take ages.

This is an attempt to sync up Makefiles to 6.1.
Unfortunately due to sheer amount of patches this is not easy to review,
but that's what we decided during a community call for the bump to 5.1,
so we are following the same guidelines here.

Signed-off-by: Sughosh Ganu 
Signed-off-by: Ilias Apalodimas a #rebased on -next

efi_loader: add dbginfodump.efi

2025-07-03T09:26:45+00:00

Provide a test application to dump the EFI_DEBUG_IMAGE_INFO_TABLE
as implemented in EDK II.

EFI_DEBUG_IMAGE_INFO is not packed in contrast to many other EFI
structures.

As of today EDK II when removing an entry in the EfiDebugImageInfoTable
just sets NormalImage = NULL but does not compact the array. So
TableSize reflects the number of non-NULL entries and not the array
size as reported independently in
https://github.com/tianocore/edk2/pull/11013 and
https://github.com/tianocore/edk2/pull/11019.

The current implementation tolerates this deviation from the UEFI
specification.

This is what the output may look like:

    Debug Info Table Dump
    =====================

    => dump
    Modified
    Number of entries: 0x0000004a
    Info type 0x00000001
      Address: [0x000000008315a000, 0x00000000831bafff]
      File: FvFile(D6A2CB7F-6A18-4E2F-B43B-9920A733700A)
      Handle: 0x000000017fe3cb18
    ...
    Info type 0x00000001
      Address: [0x000000017e8db000, 0x000000017ea00f3f]
      File: FvFile(7C04A583-9E3E-4F1C-AD65-E05268D0B4D1)
      Handle: 0x000000017f358e98
    Info type 0x00000001
      Address: [0x000000017eae5000, 0x000000017eae81ff]
      File: \dbginfodump.efi
      Handle: 0x000000017eaf0298
    =>

Signed-off-by: Heinrich Schuchardt 
Acked-by: Ilias Apalodimas 
Signed-off-by: Ilias Apalodimas

efi: add EFI_SYSTEM_TABLE_POINTER for debug

2025-07-03T09:25:47+00:00

Add EFI_SYSTEM_TABLE_POINTER structure for remote debugger to locate
the address of EFI_SYSTEM_TABLE.

This feature is described in UEFI SPEC version 2.10. Section 18.4.2.
The implementation ensures support for hardware-assisted debugging and
provides a standardized mechanism for debuggers to discover the EFI
system table.

Cc: Peter Robinson 
Cc: Simon Glass 
Signed-off-by: Ying-Chun Liu (PaulLiu) 
Reviewed-by: Ilias Apalodimas 
Tested-by: Heinrich Schuchardt 
Reviewed-by: Heinrich Schuchardt  # change memset(systab_pointer, 0 ...) -> systab_pointer->crc32 = 0;
Signed-off-by: Ilias Apalodimas

efi_loader: build with HII configuration protocol

2025-04-25T15:26:39+00:00

Without the HII configuration protocol the debug version of the UEFI shell
cannot be used.

Signed-off-by: Heinrich Schuchardt 
Acked-by: Ilias Apalodimas

efi_loader: Moved the generated ESL file to objtree

2025-04-13T14:09:17+00:00

Tom reports that generating the ESL file we need for authenticated
capsule updates fails to work on azure which expects a RO git tree.

Move it to $(objtree)

Reported-by: Tom Rini 
Signed-off-by: Ilias Apalodimas

efi_loader: Move public cert for capsules to .rodata

2025-04-11T11:25:31+00:00

commit ddf67daac39d ("efi_capsule: Move signature from DTB to .rodata")
was reverted in
commit 47a25e81d35c ("Revert "efi_capsule: Move signature from DTB to .rodata"")
because that's what U-Boot was usually doing -- using the DT to store
configuration and data. Some of the discussions can be found here [0].

(Ab)using the device tree to store random data isn't ideal though.
On top of that with new features introduced over the years, keeping
the certificates in the DT has proven to be problematic.
One of the reasons is that platforms might send U-Boot a DTB
from the previous stage loader using a transfer list which won't contain
the signatures since other loaders are not  aware of internal
U-Boot ABIs. On top of that QEMU creates the DTB on the fly, so adding
the capsule certificate there does not work and requires users to dump
it and re-create it injecting the public keys.

Now that we have proper memory permissions for arm64, move the certificate
to .rodata and read it from there.

[0] https://lore.kernel.org/u-boot/CAPnjgZ2uM=n8Qo-a=DUkx5VW5Bzp5Xy8=Wgmrw8ESqUBK00YJQ@mail.gmail.com/

Signed-off-by: Ilias Apalodimas 
Tested-by: Jonathan Humphreys   # on TI sk-am62p-lp
Tested-by: Neil Armstrong  # on AML-A311D-CC
Tested-by: Raymond Mao

efi_loader: efi_net: add EFI_HTTP_PROTOCOL

2024-12-04T11:24:38+00:00

Add an EFI HTTP driver. This commit implements the
EFI_HTTP_PROTOCOL and the EFI_HTTP_SERVICE_BINDING_PROTOCOL.
The latter is attached to the handle of th efi network
device. This is the same handle where snp, pxe, and ipconfig
are attached to.

Signed-off-by: Adriano Cordova

efi_loader: efi_net: add EFI_IP4_CONFIG2_PROTOCOL

2024-12-04T11:24:38+00:00

Add an implementation of the EFI_IP4_CONFIG2_PROTOCOL. The protocol
is attached to the handle of the efi network device. This is the same
handle where snp and pxe are attached to.

Signed-off-by: Adriano Cordova