[PATCH v5 00/12] efi_loader: more tightly integrate UEFI disks to driver model

Heinrich Schuchardt xypron.glpk at gmx.de
Mon Apr 25 22:43:44 CEST 2022


On 4/19/22 03:05, AKASHI Takahiro wrote:
> With this patch set[1] applied, UEFI subsystem maintains a list of its
> disk objects dynamically at runtime based on block device's probing.
> (See "issues" and "prerequisite" below.)
>
> [1] https://github.com/t-akashi/u-boot/tree/efi/dm_disk
>
> For instance,
> => dm tree
>   Class     Index  Probed  Driver                Name
> -----------------------------------------------------------
>   root          0  [ + ]   root_driver           root_driver
>   ...
>   pci           0  [ + ]   pci_generic_ecam      |-- pcie at 10000000
>   ...
>   ahci          0  [   ]   ahci_pci              |   |-- ahci_pci
>   scsi          0  [   ]   ahci_scsi             |   |   `-- ahci_scsi
>   usb           0  [   ]   xhci_pci              |   `-- xhci_pci
>   ...
> => efi devices
> Missing RNG device for EFI_RNG_PROTOCOL
> No EFI system partition
> Unable to find TPMv2 device
> Device           Device Path
> ================ ====================
> 000000013eee88d0 /VenHw(..)
> 000000013ffeb798 /VenHw(..)/Uart(0,0,D,D)
> 000000013eeeb810 /VenHw(..)/MAC(525252525252,1)
> => scsi rescan


With the series binding block devices after initializing the UEFI
sub-system works fine. Also unbinding is reflected in the EFI devices.

But this series breaks UEFI compliance. All block devices must be probed
before booting. Without this GRUB will not be able to read the boot
partition with vmlinuz and initrd.

Will you provide the missing patch?

Best regards

Heinrich


More information about the U-Boot mailing list