![Intel Extensible Firmware Interface Скачать руководство пользователя страница 392](http://html1.mh-extra.com/html/intel/extensible-firmware-interface/extensible-firmware-interface_specification_2073117392.webp)
Extensible Firmware Interface Specification
374
12/12/00
Version 1.02
Table G-1.
Definitions
(continued)
Term
Definition
PXE
Preboot Execution Environment
The complete PXE specification covers three areas; the client, the network and the server.
Client
•
Makes network devices into bootable devices.
•
Provides APIs for PXE protocol modules in EFI and for universal drivers in the OS.
Network
•
Uses existing technology: DHCP, TFTP, etc.
•
Adds “vendor specific” tags to DHCP to define PXE specific operation within DHCP.
•
Adds multicast TFTP for high bandwidth remote boot applications.
•
Defines Bootserver discovery based on DHCP packet format.
Server
•
Bootserver:
Responds to Bootserver discovery requests and serves up remote boot
images.
•
proxyDHCP:
Used to ease the transition of PXE clients and servers into existing network
infrastructure. proxyDHCP provides the additional DHCP information that is needed by PXE
clients and Bootservers without making changes to existing DHCP servers.
•
MTFTP:
Adds multicast support to a TFTP server.
•
Plug-In Modules:
Example proxyDHCP and Bootservers provided in the PXE 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.
UNDI
Universal Network Device Interface
UNDI is an architectural interface to NICs. Traditionally NICs have had custom interfaces and
custom drivers (each NIC had a driver for each OS on each platform architecture). Two
variations of UNDI are defined in this specification: H/W UNDI and S/W UNDI. H/W UNDI is an
architectural hardware interface to a NIC. S/W UNDI is a software implementation of the H/W
UNDI.
G.1.2 Referenced
Specifications
When implementing PXE services, protocols, ROMs or drivers, it is a good idea to understand the
related network protocols and BIOS specifications. The table below includes all of the
specifications referenced in this document.
Table G-2.
Referenced Specification
Acronym
Protocol/Specification
ARP
Address Resolution Protocol
–
http://www.ietf.org/rfc/rfc0826.txt
. Required reading for
those implementing the BC protocol.
Assigned
Numbers
Lists the reserved numbers used in the RFCs and in this specification -
http://www.ietf.org/rfc/rfc1700.txt
BIOS
Basic Input/Output System
– Contact your BIOS manufacturer for reference and
programming manuals.
continued
Содержание Extensible Firmware Interface
Страница 1: ...Extensible Firmware Interface Specification Version 1 02 December 12 2000...
Страница 4: ...Extensible Firmware Interface Specification iv 12 12 00 Version 1 02...
Страница 42: ...Extensible Firmware Interface Specification 24 12 01 00 Version 1 02...
Страница 190: ...Extensible Firmware Interface Specification 172 12 12 00 Version 1 02...
Страница 200: ...Extensible Firmware Interface Specification 182 12 12 00 Version 1 02...
Страница 226: ...Extensible Firmware Interface Specification 208 12 12 00 Version 1 02...
Страница 230: ...Extensible Firmware Interface Specification 212 12 12 00 Version 1 02...
Страница 252: ...Extensible Firmware Interface Specification 234 12 12 00 Version 1 02...
Страница 294: ...Extensible Firmware Interface Specification 276 12 12 00 Version 1 02...
Страница 348: ...Extensible Firmware Interface Specification 330 12 01 00 Version 1 01...
Страница 350: ...Extensible Firmware Interface Specification 332 12 12 00 Version 1 02...
Страница 354: ...Extensible Firmware Interface Specification 336 12 12 00 Version 1 02...
Страница 362: ...Extensible Firmware Interface Specification 344 12 12 00 Version 1 02...
Страница 486: ...Extensible Firmware Interface Specification 468 12 12 00 Version 1 02...
Страница 494: ...Extensible Firmware Interface Specification 476 12 12 00 Version 1 02...