Thank you, Andrew, for the clarification. > I don’t remember the use case for HD(0,MBR, sign) type of device path node?
don't know, how much of usability it would have per se, but representing a raw disk this way, would give an easier way to find them out. because all such would end with the same 4.1 Type.SubType and partition number. without this, a raw disk could be 3.1, or 3.25 or 3.26 or 3.29 or even 1.4 (VenHw(GUID)) or 1.1 (Pci(2, 0)) as is with OVMF for qemu arm64. And yet one thing. The Signature field in the 4.1 typed node for the case of GPT for a partition device. Did I understand correctly, that its should contain the same GUID as is in the corresponding GUID Partition Array entry field UniquePartitionGuid for that partition? Because one implementation (not edk2) puts as the Signature field DiskGuid in every partition Device Path node. -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#86131): https://edk2.groups.io/g/devel/message/86131 Mute This Topic: https://groups.io/mt/88735432/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
