Filter
Top Products
Extensible Firmware Interface Specification
12-48 12/01/02 Version 1.10
12.3.1.1 Driver Configuration Protocol
If a PCI Bus Driver or a PCI Device Driver requires configuration options, then an
EFI_DRIVER_CONFIGURATION_PROTOCOL
must be installed on the image handle in the entry
point for the driver. This protocol contains functions set the configuration information for a
controller, validate the current configuration data, and force the configuration data to its default
settings. The EFI_DRIVER_CONFIGURATION_PROTOCOL must use the standard console
devices from the EFI_SYSTEM_TABLE
to interact with the user. The functions of this protocol
will be invoked by a platform management utility. Please see the EFI Driver Model Specification
for details on the EFI_DRIVER_CONFIGURATION_PROTOCOL. Neither this specification, nor
the EFI Driver Model Specification specifies where configuration data is stored. It is up to the
driver writer to decide the appropriate location for configuration data. Some possible locations
include a FLASH device or EEPROM device that is attached to the PCI controller, or environment
variables accessed through the Runtime Services GetVariable()
and SetVariable().
12.3.1.2 Driver Diagnostics Protocol
If a PCI Bus Driver or a PCI Device Driver requires diagnostics, then an
EFI_DRIVER_DIAGNOSTICS_PROTOCOL
must be installed on the image handle in the entry
point for the driver. This protocol contains functions to perform diagnostics on a controller. The
EFI_DRIVER_DIAGNOSTICS_PROTOCOL is not allowed to interact with the user. Instead, it
must return status information through a buffer. The functions of this protocol will be invoked by a
platform management utility. Please see the EFI Driver Model Specification for details on the
EFI_DRIVER_DIAGNOSTICS_PROTOCOL.
12.3.1.3 Component Name Protocol
Both a PCI Bus Driver and a PCI Device Driver are able to produce user readable names for the
PCI drivers and/or the set of PCI controllers that the PCI drivers are managing. This is
accomplished by installing an instance of the EFI_COMPONENT_NAME_PROTOCOL
on the image
handle of the driver. This protocol can produce driver and controller names in the form of a
Unicode string in one of several languages. This protocol can be used by a platform management
utility to display user readable names for the drivers and controllers present in a system. Please see
the EFI Driver Model Specification for details on the EFI_COMPONENT_NAME_PROTOCOL.