Base cod, Protocol – Intel Extensible Firmware Interface User Manual
Page 1061

Glossary
Version 1.10
12/01/02
Glossary-13
information that is needed by PXE clients and Bootservers
without making changes to existing DHCP servers.
: Adds multicast support to a
Plug-In Modules: Example proxyDHCP and Bootservers provided in
SDK (software development kit) have the ability to take plug-
in modules (PIMs). These PIMs are used to change/enhance the
capabilities of the proxyDHCP and Bootservers.
Protocol Handler Services
The set of functions used to manipulate handles, protocols, and protocol
interfaces. Includes
Protocol Handler A function that responds to a call to a
HandleProtocol
request for a given
handle. A protocol handler returns a protocol interface structure.
Protocol Interface Structure
The set of data definitions and functions used to access a particular type of
device. For example, BLOCK_IO is a protocol that encompasses interfaces to
read and write blocks from mass storage devices. See
Protocol Revision Number
The revision number associated with a protocol. See
Protocol
The information that defines how to access a certain type of device during boot
services. A protocol consists of a
, a protocol revision number, and a
protocol interface structure. The interface structure contains data definitions and
a set of functions for accessing the device. A device can have multiple protocols.
Each protocol is accessible through the device’s handle.
PXE Base Code Protocol
A protocol that is used to control PXE-compatible devices. It is layered on top of
a
to perform packet-level transactions, and may be
used by the firmware’s boot manager to support booting from remote locations.
Also called the EFI PXE Base Code Protocol.
PXE
Read-Only Memory (ROM)
When used with reference to the
specification, ROM refers to a
nonvolatile memory storage device on a
ROM