On 09/01/2019 19:35, Aaron Young wrote:
Example output of the efimap command is as follows:
iPXE> efimap
Drive# Path
------ ----
0 PciRoot(0x0)/Pci(0x3,0x0)/HD(2,MBR,0x2E0E0369,0xBBC,0x3708)
1 PciRoot(0x0)/Pci(0x4,0x0)/HD(1,GPT,F82F29A0-...,0x800,0x64000)
2 PciRoot(0x0)/Pci(0x5,0x0)/HD(1,GPT,F82F29A0-...,0x800,0x64000)
3 PciRoot(0x0)/Pci(0x6,0x0)/HD(1,GPT,F82F29A0-...,0x800,0x64000)
4 PciRoot(0x0)/Pci(0x7,0x0)/HD(1,GPT,F82F29A0-..,0x800,0x64000)
It's reasonably common to have UEFI systems that do not provide
EFI_DEVICE_PATH_TO_TEXT_PROTOCOL, which is why efi_devpath_text() is
used only in DBG() statements.
How is this feature expected to behave (both in terms of drive ordering
and in terms of efimap output) if the protocol is not available?
Thanks,
Michael
_______________________________________________
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
