Media Device Path; Hard Drive; Vendor-Defined Messaging Device Path - Intel Extensible Firmware Interface Specification

Intel extensible firmware interface specification
Table of Contents

Advertisement

5.3.4.13 Vendor-Defined Messaging Device Path

Table 5-21. Vendor-Defined Messaging Device Path
Mnemonic
Type
Sub-Type
Length
Vendor_GUID
Vendor Defined Data
The following two GUIDs are used with a Vendor-Defined Messaging Device Path to describe the
transport protocol for use with PC-ANSI and VT-100 terminals. Device paths can be constructed
with this node as the last node in the device path. The rest of the device path describes the physical
device that is being used to transmit and receive data. The PC-ANSI and VT-100 GUIDs define the
format of the data that is being sent though the physical device. Additional GUIDs can be
generated to describe additional transport protocols.
#define DEVICE_PATH_MESSAGING_PC_ANSI \
{ e0c14753-f9be-11d2-9a0c-0090273fc14d }
#define DEVICE_PATH_MESSAGING_VT_100
{ DFA66065-B419-11d3-9A2D-0090273FC14D }
5.3.5

Media Device Path

This Device Path is used to describe the portion of the medium that is being abstracted by a boot
service. An example of Media Device Path would be defining which partition on a hard drive was
being used.

5.3.5.1 Hard Drive

The Hard Drive Media Device Path is used to represent a partition on a hard drive. The master boot
record (MBR) that resides in the first sector of the disk defines the partitions on a disk. Partitions
are addressed in EFI starting at LBA zero. Partitions are numbered one through n. A partition
number of zero can be used to represent the raw hard drive.
The MBR Type is stored in the Device Path to allow new MBR types to be added in the future.
The Hard Drive Device Path also contains a Disk Signature and a Disk Signature Type. The disk
signature is maintained by the OS and only used by EFI to partition Device Path nodes. The disk
signature enables the OS to find disks even after they have been physically moved in a system.
Version 1.02
Byte
Byte
Offset
Length
Description
0
1
Type 3 – Messaging Device Path
1
1
Sub-Type 10 – Vendor
2
2
Length of this structure in bytes. Length is 20 + n bytes.
4
16
Vendor-assigned GUID that defines the data that follows
20
n
Vendor-defined variable size data
12/12/00
Device Path Protocol
\
129

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Extensible Firmware Interface and is the answer not in the manual?

Subscribe to Our Youtube Channel

Table of Contents