Abstract: A programmable processor calculates a hash value of a memory region, then monitors program operation to detect a security monitoring system initialization. The hash value is added to extend a security measurement sequence if the security monitoring system initialization clears a security state. Processors that implement similar methods, and systems using such processors, are also described and claimed.

Abstract: A programmable processor initializes its state, then computes and verifies a hash of a boot code region of memory before executing any user instructions in the memory. Systems using similar processors, and software to control such a processor's operation, are also described and claimed.

Abstract: Processor-based systems may use more than one operating system and may have disk drives which are cached. Systems which include a write-back cache and a disk drive may develop incoherent data when operating systems are changed or when disk drives are removed. Scrambling a partition table on a disk drive and storing cache identification information may improve data coherency in a processor-based system.

Abstract: A BIOS includes a core and multiple modules. The modules include both those that are platform specific and those that are not platform specific. Each module has a standard interface that allows the core (or other module) to call the module. A platform vendor constructs a BIOS by selecting modules from one or more vendors, which when executed can select modules that are suitable for the platform the BIOS resides in.

Abstract: Briefly, in accordance with an embodiment of the invention, an apparatus and method to store initialization and configuration information is provided. The method may include storing basic input/output system (BIOS) software in a polymer memory. The method may further include copying a first portion of the BIOS software from the polymer memory to a random access memory (RAM) buffer of a memory controller, wherein the RAM buffer has a storage capacity of at least about two kilobytes (KB).

Abstract: A BIOS includes a core and multiple modules. The modules include both those that are platform specific and those that are not platform specific. Each module has a standard interface that allows the core (or other module) to call the module. A platform vendor constructs a BIOS by selecting modules from one or more vendors, which when executed can select modules that are suitable for the platform the BIOS resides in.

Abstract: Briefly, in accordance with an embodiment of the invention, an apparatus and method to store initialization and configuration information is provided. The method may include storing basic input/output system (BIOS) software in a polymer memory. The method may further include copying a first portion of the BIOS software from the polymer memory to a random access memory (RAM) buffer of a memory controller, wherein the RAM buffer has a storage capacity of at least about two kilobytes (KB).

Abstract: A boot routine is initialized in a computer by bootstrapping a volume top file (VTF) located in a first addressable location accessible upon the initializing of the boot routine and the volume top file bootstrapping a set of firmware modules.

Abstract: A programmable processor initializes its state, then computes and verifies a hash of a boot code region of memory before executing any user instructions in the memory. Systems using similar processors, and software to control such a processor's operation, are also described and claimed.

Abstract: A programmable processor calculates a hash value of a memory region, then monitors program operation to detect a security monitoring system initialization. The hash value is added to extend a security measurement sequence if the security monitoring system initialization clears a security state. Processors that implement similar methods, and systems using such processors, are also described and claimed.

Abstract: A method for updating platform firmware is disclosed. This capability is facilitated by a standard software abstraction for a firmware storage device, known as Firmware Volume (FV) that is managed through a Firmware File System (FFS). The FFS enables firmware files to be created, deleted, and updated individually. The FFS also enables a plurality of firmware files to be updated atomically by managing file state information via state bits stored in a file header of each firmware file, whereby an atomic change to a single state bit simultaneously causes the FFS to use an updated set of firmware files in place of an original set of firmware files.

Abstract: A method and system for storing and accessing firmware that is distributed across both local and remote storage devices. This capability is facilitated by a standard software abstraction for a firmware storage device, known as a Firmware Volume (FV), which enables platform firmware to be stored in a variety of types of devices, including remote storage devices that may be access via a network. Under this distributed firmware storage architecture, platform firmware code may be written in a manner such that only the early memory initiation code and code necessary to produce or access to an FV exists in the local system ROM. All other firmware components, including device initialization and OS bootstrap code, may be located remotely. As a result, the firmware code, such as a system's BIOS, may be updated by simply updating the portion of the firmware that is stored in the firmware volume.

Abstract: A BIOS system and method to initialize the platform hardware components of a computer system. An object oriented abstraction of each hardware component, the features of the hardware component to be initialized, and the initialization setting for each feature according to a common syntax is input into a BIOS database. An order of initialization is determined based on the initialization dependencies of each component. At initialization, the abstraction for each component is passed to the driver of the component wherein it is interpreted by the driver.

Abstract: The present invention provides a mechanism for independently developed firmware modules to be executed in an ordered sequence such that the services required by each module will be available when the module executes. Upon execution, each of the firmware modules provides one or more services that may be used by various components in the computer platform. In one embodiment, one or more firmware modules are stored on one or more firmware devices (FD), such as a flash memory component or other types of non-volatile storage mediums. The mechanism examines header information pertaining to each of the firmware modules in each FD and determines services that are required to be available prior to the execution of that module. Firmware modules are then executed in an order that is a function of the services each module requires (i.e., is dependent on) and the services each module produces using an iterative algorithm.

Abstract: A BIOS includes a core and multiple modules. The modules include both those that are platform specific and those that are not platform specific. Each module has a standard interface that allows the core (or other module) to call the module. A platform vendor constructs a BIOS by selecting modules from one or more vendors, which when executed can select modules that are suitable for the platform the BIOS resides in.

Abstract: A boot routine is initialized in a computer by bootstrapping a volume top file (VTF) located in a first addressable location accessible upon the initializing of the boot routine and the volume top file bootstrapping a set of firmware modules.

Abstract: A method for updating platform firmware is disclosed. This capability is facilitated by a standard software abstraction for a firmware storage device, known as Firmware Volume (FV) that is managed through a Firmware File System (FFS). The FFS enables firmware files to be created, deleted, and updated individually. The FFS also enables a plurality of firmware files to be updated atomically by managing file state information via state bits stored in a file header of each firmware file, whereby an atomic change to a single state bit simultaneously causes the FFS to use an updated set of firmware files in place of an original set of firmware files.

Abstract: A BIOS system and method to initialize the platform hardware components of a computer system. An object oriented abstraction of each hardware component, the features of the hardware component to be initialized, and the initialization setting for each feature according to a common syntax is input into a BIOS database. An order of initialization is determined based on the initialization dependencies of each component. At initialization, the abstraction for each component is passed to the driver of the component wherein it is interpreted by the driver.

Abstract: A method and system for storing and accessing firmware that is distributed across both local and remote storage devices. This capability is facilitated by a standard software abstraction for a firmware storage device, known as a Firmware Volume (FV), which enables platform firmware to be stored in a variety of types of devices, including remote storage devices that may be access via a network. Under this distributed firmware storage architecture, platform firmware code may be written in a manner such that only the early memory initiation code and code necessary to produce or access to an FV exists in the local system ROM. All other firmware components, including device initialization and OS bootstrap code, may be located remotely. As a result, the firmware code, such as a system's BIOS, may be updated by simple updating the portion of the firmware that is stored in the firmware volume.