WO2011133145A1

WO2011133145A1 - Communicating operating system booting information

Info

Publication number: WO2011133145A1
Application number: PCT/US2010/031849
Authority: WO
Inventors: Kurt Gillespie
Original assignee: Hewlett Packard Development Co LP
Current assignee: Hewlett Packard Development Co LP
Priority date: 2010-04-21
Filing date: 2010-04-21
Publication date: 2011-10-27
Anticipated expiration: 2012-10-21
Also published as: GB2491771B; US9311105B2; CN102834804A; CN102834804B; DE112010005372T5; GB201217322D0; US20130031348A1; GB2491771A

Abstract

Disclosed embodiments relate to communicating operating system booting information. A machine-readable storage medium may include instructions for reading data related to booting of an operating system of an electronic device from a non-volatile storage, instructions for writing the read data to a volatile storage prior to the booting of an operating system on the electronic device, and instructions for communicating the data written to the volatile storage to the electronic device via a serial communication interface. The machine-readable storage medium may further include instructions for receiving data, from the electronic device via the serial communication interface, related to the booting of the operating system of the electronic device and instructions for writing the received data to the non-volatile storage.

Description

200904643-1

1

Communicating Operating System Booting Information BACKGROUND

[0001] Typically, when an electronic device, such as a personal computer, is turned on by a user, it first boots an operating system. During the booting process, an electronic device may, for example, test and identify system devices. While an operating system is booting, however, the user is unable to access applications on the electronic device.

BRIEF DESCRIPTION OF THE DRAWINGS

[0002] In the accompanying drawings, like numerals refer to like components or blocks. The following detailed description references the drawings, wherein:

[0003] Figure 1 is a block diagram illustrating an embodiment of a computing system.

[0004] Figure 2 is a flow chart illustrating an embodiment of a method for communicating operating system booting information.

[0005] Figure 3 is a block diagram illustrating another embodiment of communicating operating system booting information.

[0006] Figure 4 is a flow chart illustrating an embodiment of a method for communicating operating system booting information.

[0007] Figure 5 is a block diagram illustrating another embodiment of a computing system.

[0008] Figure 6 is a block diagram illustrating an embodiment of a computing system.

DETAILED DESCRIPTION

[0009] When a user turns on an electronic device, the electronic device may begin to boot an operating system. Data related to enabling an electronic device to be able to boot an operating system, such as Basic Input/Output System (hereinafter "BIOS") data, may be stored in a non-volatile storage, for example, so that the data remains available in the storage after the electronic device is powered down and accessible the next time the electronic device is turned on. The speed at which information related to the booting of an operating system may be accessed by an electronic device affects the speed of the booting process. For example, the booting process is slowed when an electronic device waits a longer period of time to receive information used in the booting process.

[0010] An electronic device may, for example, access data related to the booting of an operating system through a serial communication interface connected to a nonvolatile storage. In some cases, however, there is an increasing amount of information communicated to an electronic device using the same serial communication interface associated with a non-volatile storage storing operating system booting information. As more information is communicated across the same interface, the speed of accessing information on the serial communication interface may be decreased, resulting in a slower booting process.

[0011] Solutions for speeding up the booting process of an electronic device may involve reworking the architecture of the electronic device or altering how booting information is controlled. For example, a buffer may be added to an electronic device to buffer data related to the booting of the operating system from a non-volatile storage prior to sending it to the electronic device. Another approach involves shadowing booting information by sending the information from the non-volatile storage to a volatile storage accessible by the electronic device, such as a main storage, to allow the electronic device to directly access operating system booting information.

[0012] In one embodiment, a virtual non-volatile storage may be used to communicate operating system booting information to an electronic device. For example, a non-volatile storage may be replaced with a virtual non-volatile storage, which may include a non-volatile storage, a volatile storage, and a processor. Prior to the booting of the electronic device, but while the electronic device is receiving power, the processor may transfer data related to the booting of the electronic device from the non-volatile storage to the volatile storage. Once the electronic device begins the booting process, the data may be communicated from the volatile storage to the electronic device along the serial communication interface. Because information typically may be more quickly accessed from a volatile storage than a non-volatile storage, the electronic device may more quickly receive the booting information.

[0013] The electronic device may send to the virtual non-volatile storage processor, such as via the serial communication interface, information to be saved for the next time the electronic device is booted. The information may include, for example, information about operating system and/or BIOS settings. The processor may store the information in the non-volatile storage. Writing data to a non-volatile storage may be a slower process compared to writing data to volatile storage. In some embodiments, the processor first stores the received information in the volatile storage, for example, so that the information may be stored more quickly and the electronic device may continue with the booting process. The processor may then transfer the information from the volatile storage to the non-volatile storage at a later time, for example, when the processor is not fulfilling requests from the electronic device.

[0014] A virtual non-volatile storage may provide advantages. For example, a virtual non-volatile storage may allow an electronic device to receive the same operating system booting information more quickly from volatile storage than from non-volatile storage, thereby speeding up the booting process. Furthermore, a virtual non-volatile storage may allow operating system data received from an electronic device to be initially stored in a volatile storage, which may allow the electronic device to more quickly continue with the booting process. A virtual non-volatile storage may free the serial communication interface in communication with the nonvolatile storage to send the information more quickly. As a result, the speed of other processes may also be increased.

[0015] A virtual non-volatile storage may provide a black box mechanism for speeding up the electronic device's booting process. A virtual non-volatile storage may be packaged and marketed as a single entity, such as a computer chip, to replace a non-volatile storage. A virtual non-volatile storage may be easily incorporated into an existing system, in some cases without making major changes to the system architecture. For example, the manner for the electronic device to request booting information may remain the same. The processor in the virtual nonvolatile storage may control and manage the storage of booting information such that the electronic device is not aware of the details of how data is being transferred between and accessed from the non-volatile and volatile storage. In addition, a virtual non-volatile storage may be used in conjunction with other solutions, such as the buffering and shadowing solutions discussed above. For example, a virtual nonvolatile storage may be shadowed such that information received from the virtual non-volatile storage processor is then stored in a volatile storage accessible by the electronic device. [0016] Figure 1 is a block diagram illustrating one example of a computing system 100. The computing system 100 may include, for example, an electronic device 102, a serial communication interface 106, and a virtual non-volatile storage 124. The electronic device 102 may be any suitable electronic device, such as a personal computer, server, or mobile phone. In one embodiment, the electronic device 102 boots an operating system 126. The operating system 126 may be any suitable type of operating system.

[0017] The serial communication interface 106 may be any suitable type of serial communication interface, such as a Serial Peripheral Interface (SPI) or an Inter- Integrated Circuit interface (I2C). The virtual non-volatile storage 124 may communicate with the electronic device 102 via the serial communication interface 106. In one embodiment, the virtual non-volatile storage 124 is included in the electronic device 102, and the virtual non-volatile storage 124 communicates with a processor or other component of the electronic device via the serial communication interface 106.

[0018] The virtual non-volatile storage 124 may include, for example, a processor 1 10, a non-volatile storage 108, and a volatile storage 1 12. In one embodiment, the virtual non-volatile storage 124 may be a computer chip. The non-volatile storage 108 may be any suitable type of non-volatile storage, such as flash memory or serial access programmable random access memory. In one embodiment, the non-volatile storage 108 stores a small amount of information, such as 16 megabytes of data. The non-volatile storage may, for example, store information related to initializing or preparing the electronic device 102, such as BIOS information, prior to starting the operating system 126. In one embodiment, the non-volatile storage stores both the BIOS and additional information.

[0019] The volatile storage 1 12 may be any suitable type of volatile storage, such as random access memory (RAM). In some implementations, the volatile storage 1 12 is the same size as the non-volatile storage 108. The volatile storage 1 12 may, for example, store information received from the non-volatile storage 108 or destined for the non-volatile storage 108.

[0020] The processor 1 10 may be a central processing unit (CPU), a semiconductor-based microprocessor, or any other hardware device suitable for retrieval and execution of instructions stored in the machine-readable storage medium 1 14. The processor 1 10 may fetch, decode, and execute instructions. In one embodiment, the processor 1 10 is a processing unit associated with a computer chip, such as a microcontroller. The processor 1 10 controls the volatile storage 1 12 and the non-volatile storage 108. In some implementations, the electronic device 102 does not directly access the non-volatile storage 108 and the volatile storage 1 12 without the assistance of the processor 1 10.

[0021] The processor may include machine-readable storage medium 1 14. The machine-readable storage medium 1 14 may be any electronic, magnetic, optical, or other physical storage device that stores executable instructions or other data (e.g., a hard disk drive, random access storage, flash storage, microcontroller storage, etc.). The machine-readable storage medium 1 14 may store, for example, non-volatile storage reading/writing instructions 1 16 for reading information from and writing information to the non-volatile storage 1 12, communicating instructions 1 18 for communicating with the electronic device 102, volatile storage reading/writing instructions 120 for reading information from and writing information to the volatile storage 112, and determining instructions 122 for determining where to read or write information. In one embodiment, the processor 1 10 is a dedicated processor exclusive for communicating between the non-volatile storage 108, volatile storage 1 12, and the electronic device 102.

[0022] Figure 2 is a flow chart illustrating one example of a method 200 for communicating operating system 126 booting information. Prior to the booting of the operating system 126, the processor 1 10 may retrieve operating system 126 booting information from the non-volatile storage 108 and write it to the volatile storage 1 12. Once the electronic device 102 initiates a boot of the operating system 126, the processor 1 10 may retrieve operating system 126 booting information from the volatile storage 1 12 and communicate it to the electronic device 102 via the serial communication interface 106. The processor 1 10 may also receive information from the electronic device 102 related to the operating system 126 and store the received information in the non-volatile storage 108.

[0023] Beginning at block 202 and moving to block 204, the processor 1 10 reads data related to booting of the operating system 126 of the electronic device 102 from the non-volatile storage 108. The information may be any information related to the booting of the operating system 126, such as information related to encryption, detection, or initialization of systems or devices. The information may include, for example, information about operating system 126 settings saved to the non-volatile storage 108 when the operating system 126 was previously booted. [0024] Moving to block 206, the processor 1 10, such as by executing the volatile storage reading/writing instructions 120, writes the read data to the volatile storage 1 12 prior to the booting of the operating system 126 on the electronic device 102. For example, the processor 1 10 may write the data to the volatile storage 1 12 when the electronic device 102 is providing power to the processor 1 10, but before the electronic device 102 begins to boot the operating system 126, such as when the electronic device 102 is plugged into a power source but before a user presses the power button. This may allow the data related to the booting of the operating system 126 to be accessible from the volatile storage 108 once a boot of the operating system 126 is initiated.

[0025] In some embodiments, the processor 1 10 writes data to the volatile storage 1 12 after booting of the operating system 126 is initiated. The processor 1 10 may in some cases write some data to the volatile storage 1 12 before the booting process begins and write more data to the volatile storage 1 12 after the booting process begins. For example, the processor 1 10 may be interrupted by the booting of the electronic device 102 before it finished copying data from the non-volatile storage 108 to the volatile storage 1 12. As a result, the processor 1 10 may be able to provide some, but not all, of the data from the volatile storage 1 12 and provide the remaining data from the non-volatile storage 108. The processor 1 10 may continue the process of transferring data to the volatile storage 1 12, for example, while the processor 1 10 is not fulfilling requests from the electronic device 102.

[0026] In one embodiment, the processor 1 10 enters a sleep state after writing the data to the volatile storage 1 12, for example, before the electronic device is turned on. By entering a sleep state, the processor 1 10 may allow the electronic device 102 to conserve power. While in the sleep state, the processor 1 10 may receive a signal indicating that the electronic device 102 is initiating a boot of the operating system 126. In response, the processor 1 10 may leave the sleep state after receiving the signal so that it is ready to communicate information to the electronic device 102 during the operating system 126 booting process. In some implementations, the processor 1 10 signals the volatile storage 1 12 to enter a sleep state after the processor 1 10 finishes writing data to the volatile storage 1 12, and the processor 1 10 may signal the volatile storage 1 12 to wake from the sleep state when a boot of the operating system 126 is initiated. In one embodiment, the processor 1 10 determines whether the processor 1 10 or volatile storage 1 12 should enter a 4643-1

7 sleep state based on the type of the electronic device 102, such as whether the electronic device 102 is a cell phone, desktop, notebook, or server computer.

[0027] Continuing to block 208, the processor 1 10, such as by executing the communicating instructions 1 18, communicates the data written to the volatile storage 1 12 to the electronic device 102 via a serial communication interface 106. The information may be communicated to the electronic device 102, for example, after the electronic device 102 initiates the booting process for the operating system 126. The processor 1 10 may communicate the data, for example, in response to a request by the electronic device 102. The processor 1 10 may provide some data, such as data related to a keyboard controller, to the electronic device 1 10 from the volatile storage 1 12 before the electronic device 102 initiates a boot of the operating system 126. In some implementations, the processor 1 10 may provide data to the electronic device 102 both before and after the operating system 126 booting process is initiated.

[0028] Moving to block 210, the processor 1 10, such as by executing the communicating instructions 1 18, receives data, from the electronic device 102 via the serial communication interface 106, related to the booting of the operating system 126 of the electronic device 102. The electronic device 102 may, for example, send operating system 126 booting settings to the processor 1 10 to be stored so that they may be available the next time the operating system 126 is booted. Proceeding to block 212, the processor 1 10, such as by executing the non-volatile reading/writing instructions 1 16, writes the received data to the non-volatile storage 108. The data may be written to the non-volatile storage 108 so that it remains available after the electronic device 102 is powered off. The method 200 then continues to a block 214 to end.

[0029] In one embodiment, the processor 1 10 writes the data received from the electronic device 102 to the volatile storage 1 12. Because information may be written more quickly to the volatile storage 1 12 than the non-volatile storage 108, this may allow the booting process to proceed more quickly. While the operating system 126 booting process is progressing separately on the electronic device 102, the processor 1 10 may write the data stored in the volatile storage 1 12 to the non-volatile storage 108. The processor 1 10 may write the data to the non-volatile storage 108 at any time, such as when it is not fulfilling requests from the electronic device 102. For example, the processor 1 10 may write the information to the non-volatile storage 108 4643-1

8 while the electronic device 102 is booting the operating system 126 or when the booting process has completed.

[0030] In one embodiment, when the electronic device 102 is low on power, such as because the electronic device 102 is low on battery power or loses its power connection, the processor 1 10, by executing the non-volatile storage reading/writing instructions 1 16, immediately writes the data stored in the volatile storage 1 12 to the non-volatile storage 108 that was not previously written to the non-volatile storage 108. For example, the power level of a notebook computer may be low because it has not been plugged into a power source to charge the battery. As another example, a desktop computer may lose its power source, but still have milliseconds of execution time remaining in order to write un-synchronized data to the non-volatile storage 108. Data stored in the volatile storage 1 12 may be lost once the electronic device 102 is powered off. To save information for the next time the operating system 126 is booted, it may be desirable to store the operating system 126 booting information in the non-volatile storage 108 before the electronic device 102 and processor 1 10 lose power. Such a system may also prevent the processor 1 10 from consuming power that may be better used for other components of the electronic device 102.

[0031] The processor 1 10 may receive a signal indicating that the power level of the electronic device 102 is below a threshold. In response, the processor 1 10 may write data stored in the volatile storage 1 12 to the non-volatile storage 108. In one embodiment, the processor 1 10 then shuts down the volatile storage 1 12 so that any future data received by the processor 1 10 from the electronic device 102 may be written to the non-volatile storage 108 and any future data sent by the processor 1 10 to the electronic device 102 may be sent from the non-volatile storage 108. Such a system may cause the virtual non-volatile storage 124 to operate more slowly, but the operation allows for data to be saved while using less power.

[0032] Figure 3 is a block diagram 300 illustrating one example of communicating operating system 126 booting information. Figure 3 illustrates changes in the data stored in the non-volatile storage 108 and the volatile storage 1 12. For example, block 302 illustrates the non-volatile storage 108 storing information about the operating system 126, such as information about a password required and password setting. Prior to the booting of the operating system 126, the processor 1 10 reads the information stored in the non-volatile storage 108 and writes it to the volatile storage 1 12. Block 304 shows the information about the password required and 4643-1

9 password settings from the non-volatile storage 108 stored in the volatile storage 1 12.

[0033] The processor 1 10 may communicate information about the password required and password settings stored in the volatile storage 1 12 to the electronic device 1 12. The electronic device 102 may send the processor 1 10 updated information about the password required setting, and the processor 1 10 may then store the received information in the non-volatile storage 1 12. For example, block 306 shows an updated value for the password required setting stored in the volatile storage 1 12. The electronic device 102 may send the processor 1 10 via the serial communication interface 106 an updated value for the password operating system 126 setting. Block 308 shows an updated value for the password setting stored in the volatile storage 1 12. The processor 1 10 may read the data stored in the volatile storage 1 12 and write it to the non-volatile storage 108, as shown by block 310.

[0034] Figure 4 is a flow chart illustrating one example of a method 400 for communicating operating system 126 booting information. In some cases, the virtual non-volatile storage 124 may operate in more than one mode. For example, in circumstances where the processor 1 10 is able to cache information about the booting of the operating system 126 in the volatile storage 108 prior to the booting of the operating system 126, the processor 1 10 may retrieve the information from the volatile storage 108. However, if the processor 1 10 is unable to cache the data in the volatile storage 108, such as because power was not provided to the electronic device 102, the processor 1 10 may retrieve the booting information from the nonvolatile storage 108.

[0035] Beginning at block 402 and moving to block 404, the processor 1 10 receives a signal indicating that the electronic device 102 is initiating a boot of the operating system 126. In some cases, the processor 1 10 may wake up from a sleep state when receiving the signal. Continuing to block 406, the processor 1 10 determines, such as by executing the determining instructions 122, whether data related to the booting of the operating system 126 of the electronic device 102 is stored in a volatile storage 1 12. For example, the processor 1 10 may have previously transferred data from the non-volatile storage 108 to the volatile storage 1 12.

[0036] The processor 1 10 may use any suitable method for determining whether data related to the booting of the operating system 126 is stored in the volatile storage 1 12, such as checking a variable indicating where the information is stored. 4643-1

10

The processor 1 10 may determine at any suitable time whether information related to the booting of the operating system 126 is stored in the volatile storage 108, such as when receiving an indication that the electronic device 102 is initiating a boot of the operating system 126 or in response to a request for information received from the electronic device 102. In some cases, the processor 1 10 may determine that information was partially cached in the volatile storage 1 12.

[0037] Proceeding to block 408, if determined that the data is stored in the volatile storage 1 12, the processor 1 10 may communicate the data stored in the volatile storage 1 12 to the electronic device 102 via the serial communication interface 106. Moving to block 410, if determined that the data is not stored in the volatile storage 1 12, the processor 1 10 may communicate to the electronic device 102 via the serial communication interface 106 data related to the booting of the operating system 126 stored in the non-volatile storage 108. In one embodiment, the data is partially cached, and the processor 1 10 transmits some data from the volatile storage 1 12 and some data from the non-volatile storage 108.

[0038] Continuing to a block 412, the processor 1 10 receives data related to the booting of the operating system 126 from the electronic device 102 via the serial communication interface 106. The data may be, for example, data related to operating system 126 settings. Proceeding to block 414, the processor 1 10 writes the received data to the non-volatile storage 108. In one embodiment, the processor first writes the data to the volatile storage 1 12 and later writes the data stored in the volatile storage 1 12 to the non-volatile storage 108. The method 400 continues to block 416 and ends.

[0039] Figure 5 is a block diagram illustrating one example of a computing system 500. Figure 5 shows the electronic device 102 communicating with the processor 1 10 via the serial communication interface 106. In one embodiment, the virtual non-volatile storage 124 contains a power storage source, such as the power storage source 528. The power storage source 528 may be connected to the processor 1 10. The power storage source 528 may be any suitable power source, such as a battery or capacitor. The power storage source 528 may be, for example, a rechargeable 3.3 volt coin cell battery. In one embodiment, the power storage source 528 is shared with a complimentary metal-oxide semiconductor (CMOS), for example, for efficiency. In one embodiment, the power storage source 528 temporarily provides power to the processor 1 10, such as for a tenth or half of a second. The power storage source 528 may provide power to the processor 1 10 4643-1

11 when the electronic device 102 is not supplying power to the processor 1 10. In some cases, the power storage source 528 provides power to the processor 1 10 even though the electronic device 102 is also receiving power from another power source.

[0040] The machine-readable storage medium may include powering instructions 530 for responding to a loss of power from the electronic device 102. Data stored in the volatile storage 1 12 may not be available the next time the electronic device 102 is turned on. However, the processor 1 10 may use power to transfer data between the volatile storage 1 12 and the non-volatile storage 108, and the volatile storage 1 12 may consume power to save data. The power storage source 528 may be used to allow transactions between the electronic device 102 and the processor 1 10 to successfully finish. The processor 1 10 may receive a signal indicating that the electronic device 102 is no longer receiving power. Once the processor 110 receives the signal, the processor 110, for example, by executing the powering instructions 530, may write un-synchronized data stored in the volatile storage 1 12 to the nonvolatile storage 108 using power from the power storage source 528 to perform the transaction.

[0041] Figure 6 is a block diagram illustrating one example of a computing system 600. Figure 6 shows the electronic device 102 communicating with the processor 1 10 via the serial communication interface 106. A second serial communication interface 634 may connect the processor 1 10 to the electronic device 102. The second serial communication interface 634 may be any suitable serial communication interface, such as a Universal Serial Bus (USB). In some cases, the second serial communication interface 634 may be capable of high speed data transfers faster than the serial communication interface 106. High speed data transfers may be useful, for example, for sending information to the electronic device 102 for running initial operating system 126 booting commands, such as commands stored in the non-volatile storage 108 related to Intel or Advanced Micro Devices (AMD) chipsets. The second serial communication interface 634 may allow the processor 1 10 to send data to the electronic device 102 more quickly and may in some implementations allow the serial communication interface 106 to be used to transmit other information. Such a system may be useful, for example, if there is a large amount of information being transferred.

[0042] In one embodiment, the processor 1 10 includes communication determining instructions 632 for determining whether to send information to the electronic device 102 via the serial communication interface 106 or the second serial 4643-1

12 communication interface 634. In one embodiment, the processor 1 10 determines which serial communication interface to use to transmit information based on the communication interface in which it receives information from the electronic device 102. For example, the processor 1 10 may send information to the electronic device 102 on the same interface in which it received a request for information from the electronic device 102.

[0043] In some cases, the processor 1 10 may send information to the electronic device via both the serial communication interface 106 and the second serial communication interface 634. For example, the electronic device 102 may determine to switch to requesting information via the second serial communication interface 634 after the booting of the operating system 126 has started, such as one third the way into the process. In some cases, the second communication interface 634 is not used by the processor 1 10 until some data has been retrieved by the electronic device 102 over the first serial communication interface 106. In one embodiment, components of the electronic device 102 unrelated to the booting of the operating system 126 may be unaware of the existence of the second serial communication interface 634. In some implementations, other components of the electronic device 102 also use the second serial communication interface 634 to communicate with the electronic device 102.

[0044] Embodiments discussed above provide advantages. For example, a virtual non-volatile storage may increase the speed of booting an operating system, thereby allowing users to more quickly begin accessing an electronic device. A virtual non-volatile storage may also free the bandwidth of a serial communication interface to transmit other types of information or information to other components of an electronic device. As a result, a virtual non-volatile storage may increase the speed for the electronic device to communicate other information across the serial communication interface. A virtual non-volatile storage may in some cases conveniently provide these speed increases by replacing a typical non-volatile storage without major architectural changes.

Claims

200904643-1 13 Claims

1. A computing device comprising:

a virtual non-volatile storage comprising:

a non-volatile storage for storing data related to the booting of an operating system of an electronic device;

a volatile storage; and

a processor configured to:

transfer data from the non-volatile storage to the volatile storage prior to the booting of an operating system of an electronic device; and

communicate data stored in the volatile storage to the electronic device via a serial communication interface.

2. The computing device of Claim 1 , further comprising a power storage source connected to the processor.

3. The computing device of Claim 1 , wherein the serial communication interface comprises a serial peripheral interface.

4. The computing device of Claim 1 , wherein the processor is further configured to communicate data stored in the volatile storage to the electronic device via a second serial communication interface capable of high speed data transfers faster than the first serial communication interface.

5. The computing device of Claim 4, wherein the second serial communication interface comprises a Universal Serial Bus.

6. A method of communicating operating system booting information, comprising: receiving, by a processor, a signal indicating that an electronic device is initiating a boot of an operating system;

determining, by the processor, whether data related to the booting of an operating system of an electronic device is stored in a volatile storage;

if determined that the data is stored in the volatile storage, communicating, by the processor, the data stored in the volatile storage to the electronic device via a serial communication interface; 200904643-1

14 if determined that the data is not stored in the volatile storage, communicating, by the processor, to the electronic device via the serial communication interface data related to the booting of the operating system stored in a non-volatile storage;

receiving, by the processor, data related to the booting of the operating system from the electronic device via the serial communication interface; and

writing, by the processor, the received data to the non-volatile storage.

7. The method of Claim 6, wherein writing the received data to the non-volatile

storage comprises:

writing, by the processor, the received data to the volatile storage; and writing, by the processor, the data stored in the volatile storage to the non-volatile storage.

8. The method of Claim 6, wherein the serial communication interface comprises a serial peripheral interface.

9. A machine-readable storage medium encoded with instructions executable by a processor for communicating operating system booting information, the machine- readable storage medium comprising:

instructions for reading data related to booting of an operating system of an electronic device from a non-volatile storage;

instructions for writing the read data to a volatile storage prior to the booting of an operating system on the electronic device;

instructions for communicating the data written to the volatile storage to the electronic device via a serial communication interface;

instructions for receiving data, from the electronic device via the serial communication interface, related to the booting of the operating system of the electronic device; and

instructions for writing the received data to the non-volatile storage.

10. The machine-readable storage medium of Claim 9, where instructions for writing data to the non-volatile storage comprise:

instructions for writing the received data to the volatile storage; and

instructions for writing the data written to the volatile storage to the non-volatile storage. 200904643-1

15 1 1 . The machine-readable instructions of Claim 9, wherein the serial communication interface comprises a serial peripheral interface.

12. The machine-readable instructions of Claim 9, further comprising:

instructions for entering a sleep state after writing the received data to the non- volatile storage;

instructions for receiving a signal indicating that the electronic device is initiating a boot of an operating system; and

instructions for leaving the sleep state after receiving the signal.

13. The machine-readable instructions of Claim 9, further comprising:

instructions for receiving a signal indicating that the electronic device is no longer receiving power; and

instructions for writing data stored in the volatile storage to the non-volatile storage.

14. The machine-readable instructions of Claim 9, further comprising:

instructions for receiving a signal indicating that the electronic device power level is below a threshold;

instructions for writing data stored in the volatile storage to the non-volatile storage; and

instructions for shutting down the volatile storage.

15. The machine-readable instructions of 9, further comprising instructions for

communicating data written to the volatile storage to the electronic device via a second communication interface configured for high speed data transfers faster than the first serial communication interface.