| United States-English |
|
|
|
![]() |
User Guide hp Integrity Superdomehp 9000 Superdome > Chapter 1 OverviewFirmware |
|
New firmware consists of many components loosely coupled by a single framework. These components are individually linked binary images that are bound together at run time. Internally, the firmware employs a software database called a device tree to represent the structure of the hardware platform and to provide a means of associating software elements with hardware functionality. The firmware incorporates the following main interfaces:
The firmware supports HP-UX 11i v2, Linux, and Windows through the Itanium® Processor Family standards and extensions and has no operating systems specific functionality included. All operating systems are presented the same interface to system firmware, and all features are available to the operating system. One exception to this is that Windows Server 2003, Datacenter does not support the latest ACPI specification (2.0). The firmware must provide legacy (1.0b) ACPI tables for that operating system. Using the acpiconfig command, the ACPI tables presented to the operating system are different. The firmware implements the standard Itanium® Processor Family interfaces with some implementation-specific enhancements that the operating system can use but is not required to use, such as Page Deallocation Table reporting, through enhanced SAL_GET_STATE_INFO behavior. Itanium® Processor Family Firmware employs a user interfaces called Pre-OS System Startup Environment (POSSE). The POSSE shell is based on the EFI standard shell. Several commands have been added to the standard EFI shell to support Hewlett-Packard value-added functionality. The new commands encompass functionality similar to BCH commands on PA-RISC machines. However, the POSSE shell is not designed to encompass all BCH functionality. They are separate and distinct interfaces. Please see the POSSE specifications for further details. The new system firmware generates event IDs, similar to chassis codes, for errors, events, and forward progress to the MP through common shared memory. The MP interprets, stores, and reflects these event IDs back to running partitions. This helps in the troubleshooting process. |
|||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||