Patent application number | Description | Published |
20110022830 | Boot Block - A machine including a processor, a boot block including an immutable segment and a mutable segment, one or more BIOS images stored on the mutable segment of the boot block, and a BIOS manager executed by the processor from the immutable segment of the boot block and configured to determine whether a BIOS of the machine is valid and launch a BIOS replacement process when the BIOS is invalid. | 01-27-2011 |
20120191960 | BOOTING COMPUTING DEVICES - Example embodiments disclosed herein relate to finding a boot loader on storage. A boot process for a computing device including storage including an extensible firmware interface aware operating system is started. The storage is searched for a boot loader associated with the extensible firmware interface aware operating system. | 07-26-2012 |
20120198113 | Time measurement of power button signal activation - Embodiments herein relate to measuring a continuous time period a power button signal is in an active state. In an embodiment, a controller is to measure the continuous time period the power button signal is in an active state, where the power button signal enters the active state when a power button is physically activated by a user to initiate a power down of a system. Further, the controller is to generate and send an interrupt to the system if the continuous time period is greater than a controller time, the interrupt having higher priority than an operating system of the system. | 08-02-2012 |
Patent application number | Description | Published |
20100077199 | Systems And Methods Of Secure BIOS Update - Systems and methods of securely updating BIOS are disclosed. One such system comprises a reprogrammable memory, a first and a second register, and comparison logic. The reprogrammable memory comprises a first portion and a protect input. The protect input is configured to disallow writes to at least the first portion when the memory protect input is at a first levels, and to allow writes to at least the first portion when the protect input is at a second level. The comparison logic is configured to drive a comparison output to a third level responsive to the first and second registers having equal values, and to drive the comparison output to a fourth level responsive to the first and second registers having different values. The comparison output is electrically coupled to the memory protect input. | 03-25-2010 |
20110113181 | SYSTEM AND METHOD FOR UPDATING A BASIC INPUT/OUTPUT SYSTEM (BIOS) - There is provided a system and method for updating a basic input output system (BIOS). An exemplary method comprises obtaining a BIOS update package comprising a BIOS image update, a BIOS Signature, and a plurality of Public Key regions, wherein each Public Key region comprises a Public Key area and a signature area. The exemplary method also comprises updating a current Public Key with a new Public Key if the new Public Key is identified in one of the Public Key regions. The exemplary method additionally comprises validating the BIOS Signature using the current Public Key. | 05-12-2011 |
20110179264 | Clearing Secure System Resources In A Computing Device - Systems and methods of clearing system resources are disclosed. One example method includes the step of detecting a failure to clear a secure portion of a system resource in a device. The method also includes the step of powering off the system resource for a period of power-off time that is sufficient to clear data from the system resource, where the power off is responsive to the failure detection. The method also includes the step of unlocking the secure portion of the system resource, where the unlock is responsive to the period of power-off time having elapsed. | 07-21-2011 |
20120017285 | SYSTEMS AND METHODS OF DETERMINING A TRUST LEVEL FROM SYSTEM MANAGEMENT MODE - Systems and methods of determining a trust level from system management mode are disclosed. One such method includes: responsive to a system management mode interrupt (SMI), determining a trust level associated with code invoking the SMI; and responsive to determining that the trust level is untrusted, granting or denying a request made by the code invoking the SMI based at least in part on a type of the request. | 01-19-2012 |
20140344491 | LOCKING A SYSTEM MANAGEMENT INTERRUPT (SMI) ENABLE REGISTER OF A CHIPSET - Example embodiments disclosed herein relate to locking a system management interrupt (SMI) enable register of a chipset. Example embodiments include at least one contact configuration register to configure a contact of a chipset, and a contact SMI enable register of a chipset to store an enable value or a disable value. In example embodiments, the disable value stored in the contact SMI enable register is to prevent the chipset from providing an SMI request to a processor in response to an SMI signal received at the contact. Example embodiments further include locking the contact SMI enable register. | 11-20-2014 |
20150039812 | Modify Executable Bits of System Management Memory Page Table - A computing device to create a system management memory page table in response to the computing device powering on. The system management memory page table includes pages with executable bits. The computing device modifies the executable bits of the pages before launching an option read only memory of the computing device. | 02-05-2015 |
Patent application number | Description | Published |
20110158260 | CROSS-SCOPE SYNCHRONIZATION OF DATA ITEM KNOWLEDGE AND CORRESPONDING METADATA - The subject disclosure relates to cross scope synchronization among different sets of nodes that synchronize the same data item(s) according to different synchronization scopes. In one aspect, create and update versions are defined for a scope in which a data item was created and updated, respectively, and create and update versions are defined for a local node shared for different groups of nodes synchronizing according to the different synchronization scopes (e.g., a server node). | 06-30-2011 |
20110246418 | SYNCHRONIZATION FRAMEWORK THAT RESTORES A NODE FROM BACKUP - Architecture for restoring nodes. After restoring a node, fix-up occurs to make the node appears as a different node than before the restore operation. The node appears as a new node, which new node knows the data up to a certain point from when the new node had the prior identity. This allows for new changes generated by the new node to flow to the other nodes in the topology, as well as have the changes that the prior identity sent to other nodes flow back to the new node. In other words, the architecture maintains information to create the new node in the topology while maintaining prior data knowledge. Additionally, item level metadata of associated data items is updated to correlate with the updated data items so that changes can be correctly enumerated and applied. This metadata update occurs across scopes of which the data items are included. | 10-06-2011 |
20120324128 | CROSS-SCOPE SYNCHRONIZATION OF DATA ITEM KNOWLEDGE AND CORRESPONDING METADATA - The subject disclosure relates to cross scope synchronization among different sets of nodes that synchronize the same data item(s) according to different synchronization scopes. In one aspect, create and update versions are defined for a scope in which a data item was created and updated, respectively, and create and update versions are defined for a local node shared for different groups of nodes synchronizing according to the different synchronization scopes (e.g., a server node). | 12-20-2012 |
20140143598 | SYNCHRONIZATION FRAMEWORK THAT RESTORES A NODE FROM BACKUP - Architecture for restoring nodes. After restoring a node, fix-up occurs to make the node appears as a different node than before the restore operation. The node appears as a new node, which new node knows the data up to a certain point from when the new node had the prior identity. This allows for new changes generated by the new node to flow to the other nodes in the topology, as well as have the changes that the prior identity sent to other nodes flow back to the new node. In other words, the architecture maintains information to create the new node in the topology while maintaining prior data knowledge. Additionally, item level metadata of associated data items is updated to correlate with the updated data items so that changes can be correctly enumerated and applied. This metadata update occurs across scopes of which the data items are included. | 05-22-2014 |