[PATCH v7 6/7] test: efi: boot: Set up an image suitable for EFI testing

[Tom Rini]

On Sat, Oct 19, 2024 at 09:24:33AM -0600, Simon Glass wrote:

> Create a new disk for use with tests, which contains the new 'testapp'
> EFI app specifically intended for testing the EFI loader.
> 
> Attach it to the USB device, since most testing is currently done with
> mmc.
> 
> Initially this image will be used to test the EFI bootmeth.
> 
> Fix a stale comment in prep_mmc_bootdev() while we are here.
> 
> For now this uses sudo and a compressed fallback file, like all the
> other bootstd tests. Once this series is in, the patch which moves
> this to use user-space tools will be cleaned up and re-submitted.
> 
> Signed-off-by: Simon Glass <sjg at chromium.org>
> 
> ---
> Here is the patch to avoid sudo and CI fallback:
> 
> [1] https://patchwork.ozlabs.org/project/uboot/patch/
> 20240802093322.15240-1-richard at nod.at/
> 
> (no changes since v1)
> 
>  arch/sandbox/dts/test.dts           |   2 +-
>  test/boot/bootdev.c                 |  18 +++++++++-
>  test/boot/bootflow.c                |   2 +-
>  test/py/tests/bootstd/flash1.img.xz | Bin 0 -> 5016 bytes

This I think best illustrates the problem with "BOOTSBOX.EFI". This
image will work for CI up until I can figure out how to get access to
free arm64 servers to run some tests on and then it will fail.

This is also an ext4 image and while the specification only says SHOULD
for being FAT32 there are practical problems with using ext4 and not
FAT32 for us (some missing features in our ext4 implementation that
prevent variables from working) and so should be done as FAT32 and not
ext4.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20241019/389d7867/attachment.sig>