From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-vs1-f53.google.com (mail-vs1-f53.google.com [209.85.217.53]) by mx.groups.io with SMTP id smtpd.web10.1995.1643336356236372077 for ; Thu, 27 Jan 2022 18:19:16 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=SPN5segJ; spf=pass (domain: gmail.com, ip: 209.85.217.53, mailfrom: vlrzprgts@gmail.com) Received: by mail-vs1-f53.google.com with SMTP id a7so1325926vsc.6 for ; Thu, 27 Jan 2022 18:19:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=YIepeF7ayFNW3dqVgyLpoYSln9Y8P4Wh3+iJDfFJZoI=; b=SPN5segJ4xWCHWLyl1gbqUR1R9loeMlf0sTXqAM/9t8IScpJkIC7+nwpGKtOG8XqX1 U5mNxqWLriRgYi+0LfJK86FvskF7XKZwKf4NrduKa0Rnzl+OvEfj84lnPSzkqDacLR5B 8rP4oESBBhTRYxIMxKJrfgjrEkAY674p9sZzrGW2UNIOgp7rIJylPkx9QL3Gu+mbNtkl yChnhs55HxPXIgGmJnQIyz1pl5t9n1NIJ1d2RK17nlfNmIELkmSqgjWCHgjw56liiPrz SeUF5JYquMbRRcFZPQBnLd7QvuHFol446WyHXz0XYXl/keJBt4ZHv8zA5ZMmhtna5Avf fQ8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=YIepeF7ayFNW3dqVgyLpoYSln9Y8P4Wh3+iJDfFJZoI=; b=BpnB1rkfW2k4gEuc7JTzpICUlN4dg+GnJVM37s7za9zg1oSfqyEXbt996gYJFiVbra Cz5j3XJPUokQUfnOF7UNEwVr+Tx5IK6sXIYu+s8oxmeDmkG4ZYz7XrM+HkCEDbQ/jfJh p/v+o52R1c6ZJ4jlIxcNKHG2fFdpdPjVJzB1WXMmJlsouNLlnQk/qCQv2Eiy9+vjQxgi DymeNBQPDQaLenNYnuUq6PJLyVYIu6YBFk/8fiUnNF5U7QbhTg0nHZz4VbKkHrnt1KHN vz3/6CXh/WKE7u7+e7ObLzc13akwtGeKZIFnh6f3i8ePUldyatO7vtTSmOuH+Apzn/u0 mOSg== X-Gm-Message-State: AOAM533dm2srZEeHrZYXYkzRESre2A203PMHP4xnXXpA9t/zFbtfjVw4 n1c+vQxul1Xns4ilX58F42YVONyiKejc67o+Zxs= X-Google-Smtp-Source: ABdhPJwsRJ/U8LaCQt4KrSrh/leMNRHoKlKyehv6pRG2wdCi7t4BtriE4dab3brtZIRaxKkpgK99nQyhFS/JBNH5JHE= X-Received: by 2002:a67:ca0d:: with SMTP id z13mr3228716vsk.9.1643336355325; Thu, 27 Jan 2022 18:19:15 -0800 (PST) MIME-Version: 1.0 Received: by 2002:ab0:59a7:0:0:0:0:0 with HTTP; Thu, 27 Jan 2022 18:19:14 -0800 (PST) In-Reply-To: <0A58CE0A-5481-4B25-95E4-5AA64D51DF44@apple.com> References: <0A58CE0A-5481-4B25-95E4-5AA64D51DF44@apple.com> From: "valerij zaporogeci" Date: Fri, 28 Jan 2022 04:19:14 +0200 Message-ID: Subject: Re: [edk2-devel] Question about Block IO protocol devices To: Andrew Fish Cc: devel@edk2.groups.io Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you, Andrew, for the clarification. > I don=E2=80=99t 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.