Patent application number | Description | Published |
20080320294 | USER SELECTABLE CONFIGURATION OPTIONS APPLICATION FOR INACCESSIBLE NONVOLATILE STORAGE AT BOOTSTRAP - Embodiments of the present invention address deficiencies of the art in respect to applying user configurable options during bootstrap and provide a novel and non-obvious method, system and computer program product for user selectable configuration options application for inaccessible nonvolatile storage at bootstrap. In one embodiment of the invention, a method for user selectable configuration options application for inaccessible nonvolatile storage at bootstrap can be provided. The method can include powering up a motherboard for a computer system and reading user selectable configuration options for the computing system from sticky bits prior to bootstrap for the motherboard. The method further can include applying the user selectable configuration options to the computing system. Finally, the method can include performing bootstrap for the motherboard subsequent to applying the user selectable configuration options. | 12-25-2008 |
20090113194 | Persisting value relevant to debugging of computer system during reset of computer system - The last value of an element of a computing system is continually stored within a first register. The element is cleared during any restart or reset of the computing system. The last value is relevant to debugging of the computing system when the computing system fails to perform as expected and/or as desired. Upon receiving an instruction to reset the computing system via a first reset signal corresponding to pressing of a reset button or a second reset signal corresponding to a baseboard management controller issuing a reset command, the last value of the element as stored within the first register is copied to a second register. The computing system is then reset. The last value of the element as stored within the second register persists within the second register during this type of reset, but is cleared during any other reset or restart of the computing system. | 04-30-2009 |
20110320671 | MOVING OWNERSHIP OF A DEVICE BETWEEN COMPUTE ELEMENTS - In an embodiment, a command is received that requests movement of ownership of a target device from an origin compute element to a destination compute element. From the origin compute element, a translation of a virtual bridge identifier to a first secondary bus identifier, a first subordinate bus identifier, and a first MMIO bus address range is removed. To the destination compute element, a translation of the target virtual bridge identifier to a second secondary bus identifier, a second subordinate bus identifier, and a second MMIO bus address range is added. From a south chip that comprises the target virtual bridge, a translation of the target virtual bridge identifier to an identifier of the origin compute element is removed. To the south chip, a translation of the target virtual bridge identifier to an identifier of the destination compute element is added. | 12-29-2011 |
20130086571 | Dynamically Updating Firmware In A Computing System - Dynamically updating firmware in a computing system, including: receiving, by a firmware update module, a request to update firmware in the computing system; receiving, by the firmware update module, a firmware update; storing, by the firmware update module, the firmware update into computer memory of the computing system; and initiating, by the firmware update module, a system management interrupt with the address in computer memory of the computing system at which the firmware update is stored. | 04-04-2013 |
20130097412 | Performing A Boot Sequence In A Multi-Processor System - Methods, apparatuses, and computer program products for performing a boot sequence in a multi-processor system are provided. Embodiments include: in response to detecting initiation of a boot sequence of the multi-processor system, initializing, by a bootstrap processor (BSP), BSP memory associated with the BSP and initializing, by an application processor, memory associated with the application processor; determining, by the BSP, whether the initialization of the BSP memory is completed; and if the initialization of the BSP memory is completed, loading, by the BSP, an operating system on the BSP memory regardless of whether the application processor has completed initialization of the memory associated with the application processor. | 04-18-2013 |
20130262912 | MANAGING HARDWARE CONFIGURATION OF A COMPUTER NODE - A computer node includes an integrated management module, a field-programmable gate array, and a plurality of individual hardware devices. The integrated management module receives a user identification and identifies an associated hardware configuration, wherein the hardware configuration identifies hardware devices to be powered off. The integrated management module may instruct the field-programmable gate array to use switches to power off the identified hardware devices without powering off other hardware devices. Optionally, a default hardware configuration may be implemented in the absence | 10-03-2013 |
20130311761 | Intelligently Loading Legacy Option ROMs In A Computing System - Intelligently loading legacy option ROMs in a computing system, including: generating, by a legacy option ROM manager, an inventory for the computing system, wherein the inventory for the computing system identifies one or more devices in the computing system; determining, by the legacy option ROM manager for each option ROM available for loading, whether a device supported by the option ROM is included in the inventory for the computing system; responsive to determining that the device supported by the option ROM is not included in the inventory for the computing system, preventing the option ROM from being loaded into an option ROM address space; and responsive to determining that the device supported by the option ROM is included in the inventory for the computing system, enabling the option ROM to be loaded into the option ROM address space. | 11-21-2013 |
20140047226 | MANAGING HARDWARE CONFIGURATION OF A COMPUTER NODE - A method and computer program product for configuring the hardware devices of a computer node are disclosed. The method comprises the computer node receiving a user identification, and identifying a hardware configuration of the computer node that is stored in association with the user identification, wherein the hardware configuration identifies a subset of the hardware devices within the computer node that are not to receive power. The hardware configuration may be stored in associated with the user identification, for example by an administrator during setup. In one option, the computer node receives the user identification during user logon to the computer node. The method further comprises controlling power to the hardware devices of the computer node to implement the identified hardware configuration without physically removing the subset of hardware devices. Power is provided to the computer node except for the subset of the hardware devices. | 02-13-2014 |
20140245445 | Preventing Propagation Of Hardware Viruses In A Computing System - Preventing propagation of hardware viruses in a computing system, including: determining, by a hardware virus detection module, whether an empty connector in the computing system is damaged, wherein the empty connector is blocked from receiving an attachable computing device by a bumper; determining, by the hardware virus detection module, whether a connector for the attachable computing device is damaged; and responsive to determining that the empty connector is not damaged and that the connector for the attachable computing device is not damaged, moving the bumper such that the empty connector is not blocked from receiving the attachable computing device. | 08-28-2014 |
20140297916 | Preventing Out-Of-Space Errors For Legacy Option ROM In A Computing System - Preventing out of legacy option ROM space errors in a computing system, including: iteratively for each option ROM in the computing system: loading, into an option ROM memory, the option ROM; executing, from the option ROM memory, the option ROM; and removing, from the option ROM memory, the option ROM. | 10-02-2014 |
20140297917 | Preventing Out-Of-Space Errors For Legacy Option ROM In A Computing System - Preventing out of legacy option ROM space errors in a computing system, including: iteratively for each option ROM in the computing system: loading, into an option ROM memory, the option ROM; executing, from the option ROM memory, the option ROM; and removing, from the option ROM memory, the option ROM. | 10-02-2014 |
20150067222 | ASSERTING PHYSICAL PRESENCE TO A TRUSTED PLATFORM MODULE BY PHYSICALLY CONNECTING OR DISCONNECTING A HOT PLUGGABLE DEVICE - A compute node includes a motherboard having a trusted platform module, and also includes a port for selectively coupling a hot pluggable device into communication with the motherboard. The compute node further includes a circuit coupled to the port for detecting a change in the physical connection of the hot pluggable device to the port and for asserting a physical presence signal to the trusted platform module in response to detecting a change in the physical connection of the hot pluggable device to the port. The change in the physical connection of the hot pluggable device to the port may include either physically connecting the hot pluggable device to the port, physically disconnecting the hot pluggable device from the port, or a combination thereof. | 03-05-2015 |
20150067308 | MANAGING PHYSICAL PRESENCE ACROSS MULTIPLE BLADES - A system includes a multi-node chassis including a chassis management module, a plurality of compute nodes, and a physical presence manual actuator for transmitting a physical presence signal to each compute node in response to manual actuation. Each server has a firmware interface, a trusted platform module, and an AND gate. The firmware interface has a general purpose input output pin for providing an enabling signal in response to a user instruction to a firmware interface setup program that communicates with the firmware interface. The AND gate has a first input receiving the enabling signal, a second input receiving the physical presence signal, and an output coupled to the trusted platform module, wherein the AND gate for a selected compute node asserts physical presence to the trusted platform module of the selected compute node in response to receiving both the enabling signal and the physical presence signal. | 03-05-2015 |
20150067309 | MANAGING PHYSICAL PRESENCE ACROSS MULTIPLE BLADES - A method uses a firmware interface setup program for a selected compute node (“node”) to cause a firmware interface to enable a trusted platform module (TPM) on the selected node to receive a physical presence (PP) signal. The selected node is selected from a plurality of nodes within a multi-node chassis, wherein each node includes a firmware interface and a TPM. A device within the multi-node chassis is manually actuated to transmit a PP signal to each of the plurality of nodes, such that each node receives the PP signal. The PP signal is asserted to the TPM of the selected node in response to both enabling the TPM of the selected node to be able to receive the PP signal and receiving the PP signal. Still further, the method allows modification of a security setting of the selected node in response to the TPM receiving the PP signal. | 03-05-2015 |
20150067896 | ASSERTING PHYSICAL PRESENCE TO A TRUSTED PLATFORM MODULE BY PHYSICALLY CONNECTING OR DISCONNECTING A HOT PLUGGABLE DEVICE - A method includes asserting a physical presence signal to a trusted platform module of a compute node in response to detecting a change in the physical connection of a hot pluggable device to a port of the compute node. The change in the physical connection of the hot pluggable device to the port is selected from physically connecting the hot pluggable device to the port, physically disconnecting the hot pluggable device from the port, and combinations thereof. Optionally, the compute node has a USB port and the hot pluggable device has a USB connector that is selectively physically connectable to the USB port. In one example, detecting a change in the physical connection of the hot pluggable device to the compute node includes detecting a voltage change on the USB port. | 03-05-2015 |