Extensible Firmware Interface Specification
5.3.2.3 Memory Mapped Device Path
Table 5-5.
Memory Mapped Device Path
Mnemonic
Type
Sub-Type
Length
Memory Type
Start Address
End Address
5.3.2.4 Vendor Device Path
The Vendor Device Path allows the creation of vendor-defined Device Paths. A vendor must
allocate a Vendor_GUID for a Device Path. The Vendor_GUID can then be used to define the
contents on the
bytes that follow in the Vendor Device Path node.
n
Table 5-6.
Vendor-Defined Device Path
Mnemonic
Type
Sub-Type
Length
Vendor_GUID
Vendor Defined Data
5.3.2.5 Controller Device Path
Table 5-7.
Controller Device Path
Mnemonic
Type
Sub-Type
Length
Controller Number
122
Byte
Byte
Offset
Length
Description
0
1
Type 1 – Hardware Device Path
1
1
Sub-Type 3 – Memory Mapped
2
2
Length of this structure in bytes. Length is 24 bytes.
EFI_MEMORY_TYPE
4
4
8
8
Starting Memory Address
16
8
Ending Memory Address
Byte
Byte
Offset
Length
Description
0
1
Type 1 – Hardware Device Path.
1
1
Sub-Type 4 – 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.
Byte
Byte
Offset
Length
Description
0
1
Type 1 – Hardware Device Path.
1
1
Sub-Type 5 – Controller.
2
2
Length of this structure in bytes. Length is 8 bytes.
4
4
Controller number.
12/12/00
(See Chapter 3.)
Version 1.02
Need help?
Do you have a question about the Extensible Firmware Interface and is the answer not in the manual?