Abstract: A firmware-based mechanism for protecting against physical attacks on ROM areas holding Authenticated Variables. A first hash of contents of at least one Authenticated Variable is created by a computing device's UEFI-compliant firmware and stored in a non-volatile storage location. Subsequently a second hash of contents of the at least one Authenticated Variable is created by the firmware and compared by the firmware to the stored hash to identify unauthorized modifications of the at least one Authenticated Variable occurring after the creation of the first hash.

Abstract: A computing device equipped with UEFI-compliant firmware is provided with added functionality via an extended firmware interface. The variable interface is called with special parameters, which redirect handling of firmware service calls. Embodiments use authenticated variables to provide security properties to the special interface, use the firmware interface to provide access to diagnostics, and use the firmware interface to provide access to system management.

Abstract: A firmware-based mechanism for protecting against physical attacks on ROM areas holding Authenticated Variables. A first hash of contents of at least one Authenticated Variable is created by a computing device's UEFI-compliant firmware and stored in a non-volatile storage location. Subsequently a second hash of contents of the at least one Authenticated Variable is created by the firmware and compared by the firmware to the stored hash to identify unauthorized modifications of the at least one Authenticated Variable occurring after the creation of the first hash.

Abstract: A computing device equipped with UEFI-compliant firmware is provided with added functionality via an extended firmware interface. The variable interface is called with special parameters, which redirect handling of firmware service calls. Embodiments use authenticated variables to provide security properties to the special interface, use the firmware interface to provide access to diagnostics, and use the firmware interface to provide access to system management.

Abstract: Firmware and/or a chipset of a computer system in an example makes a determination of a state of the computer system and sets the chipset in one of a plurality of modes based on the determination of the state of the computer system.

Abstract: According to at least one embodiment of the present invention, a system comprises a standard interface for at least one standard procedure. The system further comprises a non-standard interface for at least one non-standard procedure that is not natively supported by the standard interface. The system also comprises an interposer for intercepting procedure calls made to the standard interface and determining whether an intercepted procedure call is for invoking one of the at least one standard procedure or for invoking one of the at least one non-standard procedure. If the intercepted procedure call is for invoking one of the at least one standard procedure the interposer directs the intercepted procedure call to the standard interface, and if the intercepted procedure call is for invoking one of the at least one non-standard procedure the interposer directs the intercepted procedure call to the non-standard interface.

Abstract: A computer system includes an operating system. An advanced configuration and power interface (ACPI) system is in communication with the operating system and receives an ACPI request from the operating system. A cache is in communication with the ACPI system and receives the ACPI request from the ACPI system and provides ACPI data to the operating system via the ACPI system.

Abstract: A system for remote detection using and RFID system including a transceiver, a transponder and a fuse configured within the transponder. The transceiver is configured to send and receive radio frequency signals. The transponder is configured to receive radio frequency signals from the transceiver and to send radio frequency signals to the transceiver. The transceiver is configured to send radio frequency to the transponder thereby preventing the fuse from blowing while the radio frequency signal is received.

Abstract: An interface for handing off computer system information. The interface has a data structure stored on a computer readable medium. The data structure has fields for component data pertaining to components of a computer system. The data structure is available to be populated by a first program filling in component data using identifiers for locating the component data in the data structure. The first program is able to discover components. The component data is accessible by a second program indexing the data structure with the identifiers. The second computer program is for assisting an operating system gain the component data.

Abstract: A system-event core for monitoring system events in a cellular computer system within a parent computer system is provided. The system-event core comprises: a control register block for each cell computer system configured to mask one or more system events and configurable to be masked by a system-event manager, an input/output block operable to communicate with a computer bus, a register block operable to store data about system events, and interrupt generation logic operable to control interrupts for the cellular computer system.

Abstract: Methods for using advanced configuration and power interface (ACPI) namespaces are provided. One such method comprises: providing an ACPI namespace that includes a first ACPI functional routine and a device tree lacking at least the first ACPI functional routine; and preventing a driver from being associated with the first ACPI functional routine. Systems also are provided.

Abstract: A system comprises at least one processor, and supporting firmware for supporting at least one function of the at least one processor. The system further comprises logic operable to expand the functionality of the at least one function in a fashion that is not natively supported by the supporting firmware, and an interposer for supporting the expanded functionality of the at least one function. A method for expanding the functionality of an execution unit of a system comprises implementing an execution unit in a system, and implementing pre-existing support firmware for the execution unit in the system, wherein the pre-existing support firmware supports at least one function of the execution unit. The method further comprises implementing logic expanding the at least one function in a manner not supported by the pre-existing support firmware, and implementing an interposer to support the expansion of the at least one function.

Abstract: The firmware interface table (FIT) of IA-64 instruction set is used to populate the hardware component namespace using secondary system description table (SSDT) data, where the SSDT data describes components in the system. At boot-up time all hardware components are discovered. The Advanced Configuration Power Interface (ACPI) sub-system, in the system firmware, consumes the data set-up and loads the SSDTs from the FIT to create the namespace for the active system components.

Abstract: A system and method for using memory mapped I/O (MMIO) to manage system devices is provided. A parent device in the ACPI namespace uses (MMIO) to identify the memory addresses of its children devices. An existing, but unused, construct of ACPI is used to pass the MMIO information through the operating system (OS) to the device drivers, enabling memory to be reserved by a device, and also remain hidden to the OS. The vendor defined resource data type for long information, also known as the “vendor-long” descriptor, is used to pass the appropriate information through the OS.

Abstract: A system and method for supporting multiple operating systems with mutually exclusive requirements on a single computer system, or platform. The operating system sets an ACPI variable to identify the operating system running on the platform. The system firmware automatically comes up with a common set of functionality to satisfy all operating systems that can run on the platform. The ACPI interpreter reads the OS identifying variable upon boot-up and uses it in conditional code that depends on the operating system to fully define the operation of the system component.

Abstract: A method of passing a location of a data interface. The method involves storing a first pointer in an architected location for locating information related to a system firmware read only memory (ROM). A portion of memory is allocated for a data structure that is an interface for handing off system component information. A second pointer is stored in a memory location pointed to by the first pointer. The second pointer points to the data structure.

Abstract: The present system and method allows for a memory location, typically a system event register, present in a processor to be accessed as either big or little endian mode, depending on an operating system (OS) accessible bit for endian selection. The OS type is determined at boot time.

Abstract: Methods for using advanced configuration and power interface (ACPI) namespaces are provided. One such method comprises: providing an ACPI namespace that includes a first ACPI functional routine and a device tree lacking at least the first ACPI functional routine; and preventing a driver from being associated with the first ACPI functional routine. Systems also are provided.

Abstract: Methods for building advanced configuration and power interface (ACPI) namespaces are provided. One such method comprises: providing a first ACPI functional routine; and building an ACPI namespace that includes a device tree lacking at least the first ACPI functional routine. Systems also are provided.

Abstract: Methods for using secondary system description tables (SSDTs) are provided. One such method comprises: providing a differentiated system description table (DSDT) and a first SSDT, the first SSDT including information corresponding to a first device; and using the DSDT and the first SSDT to build an ACPI namespace that includes a first ACPI functional routine and a device tree lacking at least the first ACPI functional routine. Systems also are provided.