beautypg.com

3 memory mapped device path, 4 vendor device path, 5 controller device path – Intel Extensible Firmware Interface User Manual

Page 226

background image

Extensible Firmware Interface Specification

8-6

12/01/02

Version 1.10

8.3.2.3

Memory Mapped Device Path

Table 8-5.

Memory Mapped Device Path


Mnemonic

Byte
Offset

Byte
Length


Description

Type 0

1

Type

1

– Hardware Device Path.

Sub-Type 1

1

Sub-Type

3

– Memory Mapped.

Length

2

2

Length of this structure in bytes. Length is 24 bytes.

Memory Type

4

4

EFI_MEMORY_TYPE

. Type

EFI_MEMORY_TYPE

is

defined in the

AllocatePages()

function description.

Start Address

8

8

Starting Memory Address.

End Address

16

8

Ending Memory Address.

8.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

n

bytes that follow in the Vendor Device Path node.

Table 8-6.

Vendor-Defined Device Path


Mnemonic

Byte
Offset

Byte
Length


Description

Type 0

1

Type

1

– Hardware Device Path.

Sub-Type 1

1

Sub-Type

4

– Vendor.

Length

2

2

Length of this structure in bytes. Length is 20 + n bytes.

Vendor_GUID

4

16

Vendor-assigned GUID that defines the data that follows.

Vendor Defined Data

20

n

Vendor-defined variable size data.

8.3.2.5 Controller Device Path

Table 8-7.

Controller Device Path


Mnemonic

Byte
Offset

Byte
Length


Description

Type 0

1

Type

1

– Hardware Device Path.

Sub-Type 1

1

Sub-Type

5

– Controller.

Length

2

2

Length of this structure in bytes. Length is 8 bytes.

Controller Number

4

4

Controller number.