On Sun, 19 Oct 2025 10:48:37 -0600 Tom Rini <[email protected]> wrote:
> On Sun, Oct 19, 2025 at 02:05:51PM +0100, Simon Glass wrote: > > Hi Kory, > > > > On Mon, 13 Oct 2025 at 14:32, Kory Maincent (TI.com) > > <[email protected]> wrote: > > > > > > This series converts the extension board framework to use UCLASS as > > > requested by Simon Glass, then adds extension support to pxe_utils > > > and bootmeth_efi (not tested) to enable extension boards devicetree load > > > in the standard boot process. > > > > > > I can't test the imx8 extension scan enabled by the > > > imx8mm-cl-iot-gate_defconfig as I don't have this board. > > > I also can't test the efi bootmeth change as I don't have such board. > > > > You can test this with sandbox, using one of the bootmeth tests, > > perhaps. Let me know if you need help with this. > > But the question is, does the real hardware platform work before/after > this, not does the sandbox test still work before/after this. It seems the bootlflow scan is not working on the sandbox on next branch. Is this issue known? => bootflow scan -l Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- Scanning global bootmeth 'efi_mgr': efi_var_to_file() Cannot persist EFI variables without system partition efi_tcg2_register() Missing TPMv2 device for EFI_TCG_PROTOCOL efi_rng_register() Missing RNG device for EFI_RNG_PROTOCOL Hunting with: simple_bus Found 2 extension board(s). Hunting with: mmc Hunting with: nvme Hunting with: qfw Hunting with: scsi scanning bus for devices... Hunting with: spi_flash Hunting with: virtio Scanning bootdev 'qfw_sandbox.bootdev': [1] 487232 segmentation fault (core dumped) ./u-boot Regards, -- Köry Maincent, Bootlin Embedded Linux and kernel engineering https://bootlin.com
