u-boot.git/lib/efi_loader, branch v2025.01-rc1

efi_loader: remove ERROR:, WARNING: prefixes in messages

2024-10-18T15:05:19Z

We should not write "ERROR:" or "WARNING:" when using log_err() or log_warning(). These prefixed don't provide additional information. Reviewed-by: Ilias Apalodimas Signed-off-by: Heinrich Schuchardt

efi_loader: add missing lf in error message

2024-10-18T15:05:12Z

Messages written with log_err() should terminate with a linefeed. Reviewed-by: Ilias Apalodimas Reviewed-by: Simon Glass Signed-off-by: Heinrich Schuchardt

efi_loader: reduce noisiness if ESP is missing

2024-10-18T14:17:29Z

EFI variables can be stored in a file on the EFI system partition. If that partition is missing we are writing two error messages per variable. This is too noisy. Just warn once about the missing ESP. Signed-off-by: Heinrich Schuchardt Reviewed-by: Ilias Apalodimas

efi_loader: avoid #ifdef in efi_setup.c

2024-10-18T14:17:29Z

We prefer `if` over `#ifdef` in our code. Eliminate #ifdef statements in efi_setup.c. Reviewed-by: Ilias Apalodimas Signed-off-by: Heinrich Schuchardt

efi_memory: rename variable to highlight overlap with free memory

2024-10-15T19:45:30Z

The variable overlap_only_ram is used to specify that the new memory region that is being created needs to come from the free memory pool -- this is done by carving out the memory region from the free memory. The name is a bit confusing though, as other allocated memory regions, like boot-services code and data are also part of the RAM memory. Rename the variable to overlap_conventional to highlight the fact that it is the free/conventional memory that is being referred to in this context. Signed-off-by: Sughosh Ganu Reviewed-by: Ilias Apalodimas Reviewed-by: Simon Glass

efi_memory: do not add RAM memory to the memory map

2024-10-15T19:45:30Z

The EFI_CONVENTIONAL_MEMORY type, which is the usable RAM memory is now being managed by the LMB module. Remove the addition of this memory type to the EFI memory map. This memory now gets added to the EFI memory map as part of the LMB memory map update event handler. Signed-off-by: Sughosh Ganu Reviewed-by: Simon Glass Reviewed-by: Ilias Apalodimas

efi_memory: do not add U-Boot memory to the memory map

2024-10-15T19:45:29Z

The memory region occupied by U-Boot is reserved by LMB, and gets added to the EFI memory map through a call from the LMB module. Remove this superfluous addition to the EFI memory map. Signed-off-by: Sughosh Ganu Reviewed-by: Ilias Apalodimas

lmb: notify of any changes to the LMB memory map

2024-10-15T19:45:29Z

In U-Boot, LMB and EFI are two primary modules who provide memory allocation and reservation API's. Both these modules operate with the same regions of memory for allocations. Use the LMB memory map update event to notify other interested listeners about a change in it's memory map. This can then be used by the other module to keep track of available and used memory. There is no need to send these notifications when the LMB module is being unit-tested. Add a flag to the lmb structure to indicate if the memory map is being used for tests, and suppress sending any notifications when running these unit tests. Signed-off-by: Sughosh Ganu

efi: memory: use the lmb API's for allocating and freeing memory

2024-10-15T19:45:29Z

Use the LMB API's for allocating and freeing up memory. With this, the LMB module becomes the common backend for managing non U-Boot image memory that might be requested by other modules. Signed-off-by: Sughosh Ganu

efi_loader: Show FirmwareVendor and FirmwareRevision in helloworld

2024-10-10T04:04:56Z

Show the firmware vendor and revision to make it clear which firmware is used, e.g. whether U-Boot is providing the boot services. The output will look like Firmware vendor: Das U-Boot Firmware revision: 20241000 Signed-off-by: Simon Glass Signed-off-by: Heinrich Schuchardt