[U-Boot] [PATCH 00/23] efi_loader implement missing functions
leif.lindholm at linaro.org
Thu Aug 31 14:45:35 UTC 2017
On Wed, Aug 30, 2017 at 08:59:31AM +0100, Leif Lindholm wrote:
> On Wed, Aug 30, 2017 at 12:03:16AM +0200, Heinrich Schuchardt wrote:
> > I am able to provide a test application that will cover the API
> > functions that I have focused on (events, protocols, (dis)connect
> > controllers). To limit my effort I would like to write it for the HEAD
> > of my patch queue and not break it down into one test patch per
> > implementation patch. I hope that is ok for you. My effort estimate is
> > 40h+ so, please, be patient.
> I am not going to claim that getting SCT to run under U-Boot is going
> to come near the top of my priority queue any time soon, and it would
> certainly be useful for some sort of "make sure we don't break what we
> have" tests.
Well, I spent a few hours looking at what the immediate issues may be
with running the UEFI Shell (built with -D NO_SHELL_PROFILES), same as
edk2/ShellBinPkg/MinUefiShell. Alex suggested I post an update.
I've implemented stubs for the missing protocols preventing the Shell
from starting properly, and pushed everything to
(As Alex points out, I forgot about the EFI_EXIT/EFI_ENTER macros.)
With this, execution fails with
Found 2 disks
ASSERT_EFI_ERROR (Status = Device Error)
"Synchronous Abort" handler, esr 0x5600dbdb
The AutoGen.c failure is a library constructor
(ShellLevel2CommandsLibConstructor) returning error because
MdeModulePkg/Library/UefiHiiLib/HiiLib.c : HiiAddPackages() received
an error return from new_package_list (in the non-camel-case u-boot
If you could look into implementing something useful in that function,
I could look into what causes the next stumbling block after that.
I did overrun the "maximum number of open protocols" limit, so
randomly bumped that up to 12. It will need to go higher (and
preferably dynamic). As long as we're not planning to support
protocols staying around at runtime, I'd say that shouldn't be too
hard to resolve properly.
I have pushed an update to the pre-built versions of UEFI Shell in edk2:
These are built without ASSERTs, so won't actually give the above
messages, but should otherwise be identical to the one I've used here.
More information about the U-Boot