Media Device Path Rules; Other Rules - Intel Extensible Firmware Interface Specification

Intel extensible firmware interface specification
Table of Contents

Advertisement

Extensible Firmware Interface Specification
5.4.5

Media Device Path Rules

The Media Device Path is used to define the location of information on a medium. Hard Drives are
subdivided into partitions by the MBR and a Media Device Path is used to define which partition is
being used. A CD-ROM has boot partitions that are defined by the "El Torito" specification, and
the Media Device Path is used to point to these partitions.
A
protocol is produced for both raw devices and partitions on devices. This allows the
BLOCK_IO
SIMPLE_FILE_SYSTEM
protocol for a partition contains the same Device Path as the parent
raw device with the addition of a Media Device Path that defines which partition is being
abstracted.
The Media Device Path is also used to define the location of a file in a file system. This Device
Path is used to load files and to represent what file an image was loaded from.
5.4.6

Other Rules

The BIOS Boot Specification Device Path is not a typical Device Path. A Device Path containing
the BIOS Boot Specification Device Path should only contain the required End Device Path
structure and no other Device Path structures. The BIOS Boot Specification Device Path is only
used to allow the EFI boot menus to boot a legacy operating system from legacy media.
The EFI Device Path can be extended in a compatible fashion by assigning your own vendor GUID
to a Hardware, Messaging, or Media Device Path. This extension is guaranteed to never conflict
with future extensions of this specification
The EFI specification reserves all undefined Device Path types and subtypes. Extension is only
permitted using a Vendor GUID Device Path entry.
136
protocol to not have to understand media formats. The
12/12/00
BLOCK_IO
protocol for the
BLOCK_IO
Version 1.02

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?

Table of Contents