public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "valerij zaporogeci" <vlrzprgts@gmail.com>
To: Andrew Fish <afish@apple.com>
Cc: devel@edk2.groups.io
Subject: Re: [edk2-devel] Question about Block IO protocol devices
Date: Fri, 28 Jan 2022 04:19:14 +0200	[thread overview]
Message-ID: <CANPuzFw=WDr3DqHQXC4iK9+HEq=d9aqvmPn9f3Ui1Zpn=M-PTg@mail.gmail.com> (raw)
In-Reply-To: <0A58CE0A-5481-4B25-95E4-5AA64D51DF44@apple.com>

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.

  reply	other threads:[~2022-01-28  2:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  0:34 Question about Block IO protocol devices valerij zaporogeci
2022-01-28  1:28 ` [edk2-devel] " Andrew Fish
2022-01-28  2:19   ` valerij zaporogeci [this message]
2022-01-28  3:19     ` Andrew Fish
2022-01-28  3:45       ` valerij zaporogeci

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANPuzFw=WDr3DqHQXC4iK9+HEq=d9aqvmPn9f3Ui1Zpn=M-PTg@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox