Hi Heinrich, On Sat, 23 Oct 2021 at 06:31, Heinrich Schuchardt <xypron.g...@gmx.de> wrote: > > > > On 9/25/21 02:30, Simon Glass wrote: > > At present UCLASS_EFI is used to represent an EFI filesystem among other > > UCLASS_EFI is for UEFI drivers that provide the driver binding protocol. > > Your new UCLASS seems to be for U-Boot drivers consuming the > EFI_BLOCK_IO_PROTOCOL. > > I agree that lib/efi_driver/efi_block_device.c is to much intertwined > with the UEFI subsystem to easily merge it with your requirement. But it > at least can serve as a template.
It did. > > > things. The description of this uclass is "EFI managed devices" which is > > pretty vague. The only driver that uses this uclass is in fact not a real > > U-Boot driver, since its operations do not include a struct udevice. > > > > Rather than mess with this, create a new UCLASS_EFI_MEDIA uclass to handle > > EFI media such as disks. Make this the uclass to use for EFI media so that > > In UEFI speak MEDIA relates to: > > * block devices > * firmware files > * Bluetooth > * REST services > * etc > > Do you only mean block devices? Sort of...it is a parent of a block device, like MMC or SCSI. > Why can't you use UCLASS_BLK for your new driver? That is the child. I need something to be the parent so that it actually works. Regards, Simon
