TWI307838B - - Google Patents

Description

1307838 IX. Description of the Invention: [Technical Field] The present invention relates to a method for reading memory space efficiency, in particular, a structure of a universal extendable firmware interface/extensible fine interface The method of using read-only memory space efficiency. [Prior Art] Due to the rapid advancement of computer technology, the traditional basic output system (Legacy BIOS) with the development of computer systems has reached its limit. Therefore, in order to overcome the bottleneck in the development of the traditional basic input and output system, Intel Corporation has developed a 'extensible firmware interface' (EFI, Extensible Firmware Interface) specification, which eliminates the basic input and output system. Innate limitations. Moreover, this extensible firmware interface allows for the addition of new components using standard programming language tools, with better scalability, and is written in C, which is easy to maintain and read. However, Intel's extendable interface for firmware can only be used for specific CPUs. In view of this, Intel △ Division and the company that manufactures CPUs have developed a universal extendable firmware interface (ie UEFI, Universal Extensible Firmware

Interface) is suitable for cpu manufactured by various companies. After the computer is powered on, the CPU (Central Processing Unit) reads the required drivers from the universal extendable firmware interface/extensible firmware interface stored in the read-only memory (such as flashpart). The program is used for self-testing and import and output interface search and setting. 326\patent specification (supplement)\95-05\TF954507 5 1307838 When the computer system is applied to the architecture of the universal extendable firmware interface/extensible WEI blade interface, the computer system will be in the stage of the boot process. carried out

Individual PEIM (PEI) in the PEI (Pre-EFI Initialization) phase

Module), to initialize the computer system's main architecture such as memory, bus and system clock, etc. Then, the computer system will execute the driver in the DXE (Driver Execution Environment) stage. Initialize settings for other architectures of the computer system, such as the peripheral interface. FIG. 1 is a schematic diagram showing the configuration of a read-only memory under the architecture of a universal extendable firmware interface/extensible firmware interface. In Fig. 1, the read-only memory 10 includes an EC (Embedded Controller) section 12, a DxeMain (Driver Execution).

Environment Main) section 14, a NVSorage (Non-volatile Storage) section 16 and an FvRecovery (Firmware volume Recovery) section 18, etc., and the NVSorage section 16 includes a Variable section 20, a Microcode section 22, An Event Log section 24, a FTW Working (FauIt Tolerant Write Working) section 26, and an FTW Spare (Fault Tolerant Write Spare) section 28, and the like. In the Variable section 20, the variable data required for booting is stored, and the variable data includes the variable data that has been deleted. When the variable data stored in the Variable section 20 is full, the variable to be added is added. The data cannot be stored in the Variable section 20, and the variable data in the Variable section 20 is 326\patent specification (supplement)\95-〇5\TF954507 6 1307838 in the FTW Spare section 28. In order to clear the unused variable data, the reorganization procedure is as shown in the process diagram of the variable data in the reforming Variable section of the prior art. In FIG. 2, first, it is judged in the variable section 20 whether the new variable data and the previous variable data are the same name but not the same content (step S30) 'When the new variable data is the same as the previous variable data If the name but not the same content, the previous variable data is set to an old data flag (step S32); when the new variable data and the previous variable data are not the phase = name or the previous variable data has been set After the old data flag, it is judged whether the variable data in the Variable section 20 is full (step S34), and when the variable data in the variable section 20 is full, the Variable section 20 and the MicroCode area are executed. The data of the segment 22, the Event L〇g segment 24, and the FTW Working segment 26 are copied into the FTW Spare section 28 (step S36). Then, in the FTW Spare section 28, the variable data of the Variable section is reorganized, and the reconstructed variable data is cleared by the data variable marked with the deletion token, and the reconstructed variable data, Micr〇c The data of the 〇de section 22, the Event Log section 24 and the FTW Working section 26 are copied back to the Variable section 20 Microcode section 22, Event

The Log section 24 and the FTW Working section 26 (step S38). Among them, the 忒 re-routing procedure can be completed by a program familiar to those skilled in the art in accordance with the specifications of the Universal Extensible Firmware Interface/Extensible Firmware Interface. Next, clear all the data in the FTWSpare section 28 (step S4〇), 326 pass the instructions (supplement)\95-〇5\TF954507 7 1307838 to wait for the next re-formation Var i ab 1 e section 20 variable Information procedure. Secondly, after the variable data in the Variable section 20 is not full or after all the data in the FTW Spare section 28 has been cleared (ie, the reforming process is completed), the newly added variable data is stored in the Variable section 20 in the previous section. After the variable data (step S42). Furthermore, it is determined whether the previous variable data has the old data flag set (step S44), and when the previous variable data does not set the old data flag, it indicates that the new variable data does not have the same name as the previous variable data. Then all the above processes are completed; when the previous variable data is set with the old data flag, indicating that the new variable data is the same name as the previous variable data but not the same content, the variable of the old data flag will be set. The data is marked with the deletion mark (step S46). So, all the above processes are completed. The conventional technique requires a memory space (ie, FTW Spare section 28) in the read-only memory to perform the copy variable section 20, the M/croCode section 22, the Event Log section 24, and the FTW Working zone. 6 = bedding, and perform the variable data in the Var丨e section 2 重 re-check this purpose, in order to prevent the computer from being powered off if the computer suddenly powers off during the re-execution process The resulting data is corrupted by the machine. However, when the reforming private sequence of the number of bucks in the Variable section 20 is not executed, the space of the FTW unloading section 28 is idle. fRead the memory space. SUMMARY OF THE INVENTION The object of the present invention is to provide 唯^^^^, 钕 for a read-only memory space efficiency in a general-purpose extendable firmware interface/"Tk stretch-type initial interface. 326 method of transfer (supplement) \95-05\TF954507 1307838 'This method is to make the 唯 in the read-only memory to execute the cup in the Variable section _ 1 ° °, in the side of l only γ The data is heavy in the FTW Spare section, and the driver is using the Μ 6A # ^ ^ 仃Variable section of the variable 10 滑^ under the condition, by AL, r ff ^ , his driver Or use of data, so that the space of the read-only memory can be effectively utilized. The present invention provides a method for using read-only memory space efficiency under the architecture of a universal extendable (four) interface/extensible wiper interface. The read-only memory has a -Nm〇rage segment, the plus The fraud section has a Variable section, a Micr〇c〇de section, a Log section, a FTW Working section, and an FTW Spare section, where the FTW Spare section stores drivers or materials when the Variabie When the data of the segment is full and needs to be reformed, the method of using the read-only memory space under the architecture of the universal extendable firmware interface/extensible firmware interface includes the following steps: First, the FTW The driver or data stored in the Spare section is copied to a storage device and the FTW Lu Spare section is cleared; then the Variable section, the Microcode section, the Event Log section, and the FTW Working section are The data is copied to the FTW Spare section; secondly, the variable data of the Variable section is reformed in the FTW Spare section, and the reformed variable data, the Microcode section, the Event Log section, and the FTW are reconstructed. Work The data of the ing section is copied back to the Variable section, the Microcode section, the Event Log section, and the FTW Working section; then 'clear the FTW Spare section; and the driver copied by the storage device Or copy the information back to the FTW Spare section. 326 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 3 is a schematic diagram of a section of a read-only memory for storing data relative to a data body in an FTW Spare, and FIG. 4 is a flow chart of variable data in a reformed Variable section of the present invention. 4 and FIG. 2 have the same private steps and are omitted in FIG. 4, and the same reference numerals as in FIG. 2 are used to explain the flow of FIG. • In Figure 3, 'when the computer is turned on, the var丨ab 1 e is not executed in the reorganization of the variable data in the section 20'. The FTW Spare section 28 has a data body section 5 for storing drivers or data. A PEI and/or DXE program section 52 is defined in the read-only memory i, and the PEI and/or DXE program section 52 has a New section mark 54, a size 56, and a data body area. Segment size 58 and data body segment indicator 6〇 and other data. φ where the data in the New section mark 54 is the name of the PEI and/or DXE program section 52. The data in the Size 56 indicates the size of the PEI and/or DXE program section 5 2 'data body section size within 5 8 The data description data body section 50 uses the data size of the FTW Spare section 28's data onto the data body section indicator 60 to indicate the address of the data body section 50 of the FTW Spare section 28. In addition, the Di spatcher private version needs to be modified to correctly recognize the newly added New section mark 54 °. The driver or data stored in the data body section 50 can be the program 326\patent specification (supplement). \95-05\TF954507 10 1307838 The hair is used as a debugging tool or can be driven by the driver and the function of the additional function. For such application, the gentleman uses the read-only memory 1G. The purpose of the "_^ effective data is that even in the reforming of the Var乂' sub-distribution of this special driver or Mr, the variable in the Dong i Variable section 20 is cautious = for some reason, such drive or shell After the computer is turned on, use the general-purpose P1, the extended firmware, and the I-face/extensible toughness.

s as 1 has such drivers or data written back to the FTW at 28' without causing the computer to fail to boot. When the computer is turned on, if you want to rebuild the material, as shown in Figure 4;;ar:;b=2" variable 20 Φ jk,i ^ ^ 斤 first, in the Variable section = broken new Whether the variable data and the previous variable data are the same name (step S3.), when the new variable data is the same as the content, the previous variable is: variable data n s32); # new variable data and previous When the same name is used or the previous data flag has been changed, then judge /v · 贪 贪 贪 疋 疋 疋 疋 廿 廿 廿 廿 = = = = = = = = = = = = = = = = Step S34), when the terapox in the variable section 20 is full, the driver or the data stored in the data section 50 of the FTW Spare section 28 is copied to a storage device. Display and clear all the information in the FTWSpare section 28 (in the step, Cai Wei, 'the storage device can be a random access memory, a non-volatile memory or a hard disk, etc., in order to avoid sudden power failure of the computer, The driver or data can be copied to non-volatile memory or hard disk. Second: After the Variable area 20, Microcode section 22, Event 32 said patent specification (complement member) \ 95-05 \ TF954507 "1307838

The data of the Log section 24 and the FTW Working section 26 is copied into the FTf S text section 26 (step S36). In the FTW Spare section 28, the variable data of the Varlable section is reorganized, and the variable data of the reorganization is cleared by the data variable with the de-marked mark' and the variable after the reformation

Shell material, Mlcr〇C〇de section 22, Event Log section 24 and FTW

The working section 26 data is copied back to the Variabie section.

The Microcode section 22, the Event Log section 24, and the FTW forking section 26 (step S38). Among other things, the reforming procedure can be accomplished by procedures familiar to those of ordinary skill in the art in accordance with the specifications of the Universal Extensible Weaver Interface/Extensible Firmware Interface. Then, in addition to all the data in the FTW Spare section 28 (the steps are to copy the driver or data copied from the storage device back to the location of the data body section 5 of the FTW section (step s 7 2), Avoid the data body segment index 6〇 pointing to the address of the data body segment 5〇. Secondly, when the variable data in the Variable segment 20 is not full or the driver or data copied by the Lu storage device is copied back In the position of the data body section 50 of the FTW s yang re section 28, the newly added variable data is stored in the Var i ab 1 e section 20 in the previous variable data (steps are determined by 2^ again) Whether the previous variable data has the old data flag set (step S44), and when the previous variable data does not set the old data flag τ, indicating that the new variable data does not have the same name as the previous variable data, the above is completed. All processes; when the previous variable data is set with the old data flag, indicating that the new variable data and the previous variable data are the same name but not the same content, the old data flag will be set 326 Passing the instruction manual (supplement)\95-05\TF954507] 2 1307838. Thus, the above number data is marked with the deletion mark (step S46). All the advantages of the present invention are the FTW s in the read-only memory. _ section, in the case of the reorganization of the variable data in the executable section, the FTW Spare section can be utilized, and the reorganization of the variable data in the S Var i ab 1 e section is not available Other drivers or data utilization, which will effectively increase the space of the original program area & to put more drivers or sell materials, and effectively use the space of the read-only memory. Although the present invention has been referred to The present invention is not limited by the scope of the present invention. The present invention is not limited to the scope of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic diagram showing the configuration of a read-only memory under the architecture of a universal extendable firmware interface/extensible firmware interface; FIG. 2 is a prior art reforming var i ab 1 Variables in the e section FIG. 3 is a schematic diagram of a section of a read-only memory for storing data relative to a data body in an FTW Spare; and FIG. 4 is in the reforming variable section of the present invention. Flow chart of variable data. [Main component symbol description] 1 〇 Read only memory 12 EC section 326\Patent specification^甫)\95_〇5yrF9545〇7 13 1307838 14 DxeMain Section 16 NVStorage Section 18 FvRecovery Zone Segment 20 Variable Section 22 MicroCode Section 24 Event Log Section 26 FTW Working Section 28 FTW Spare Section 50 Data Body Section 52 PEI and/or DXE Program Section 54 New section mark 56 Size 58 Data Ontology Section Size 60 data ontology segment indicator 326\patent specification (supplement)\95-05\TF954507 14

Claims (1)

1307838 X. Patent Application Range: 1. A method for the read-only memory space usage efficiency under the general extension of the firmware interface/extensible firmware interface, the read-only memory has a 'Storage area Segment, the NVSt〇rage section has a Vanable section, a Micr〇c〇de section, an Event L〇g section, an FTW Working section, and a Spare section, and the FTW Spare section stores the driver Program or data, when the data of the VariaMe section is full and needs to be reformed, the read-only memory space usage method under the architecture of the universal extendable firmware interface/extensible firmware interface includes the following steps: Copy the driver or data stored in the FTW Spare section to a storage device' and clear the FTW Spare section; the 5H Recreation section, the Microcode section, the Event Log section, and the FTW Working section The data is copied to the FTW Spare section; the variable data of the Variable section is reorganized in the FTW Spare section and the reconstructed variable data, the Microcode section 'the Event Log section and the FTW The working section data is copied back to the Variable section, the Microcode section, the Event Log section, and the FTW Working section; the FTW Spare section is cleared; and the driver or data copied by the storage device is copied. Go back to the FTW Spare section. 2. For example, in the scope of the patent application, the method of read-only memory under the framework of the universal extendable firmware interface / 326 patent specification (supplement) \95-05\TF954507 15 1307838 2 The following steps are included: The two use efficiency determines whether the new variable data is the same name but not the same content in the Variable section; the material and the previous variable are when the new variable data is the same as the previous variable. Then, the previous variable data is set to the same name but not quite new variable data and the previous variable ic flag; if the previous variable data has been set with the same name of the old two or the variable data in the Variable section has been saved If it is not full, it is judged that the variable data in the Variable section is already present, and the driver program stored in the m Spare section executes the storage device and clears the step of the FTW Spare section. When the driver copied by the variable storage device in the Variable section is copied back to the full storage or the newly added variable data and data are stored in the pare section, the variable data is stored; In the money ri_e section, it is previously determined whether the previous variable data is set. When the previous variable data is set with the old asset 2::flag; and the variable information of the sales pitch flag is marked with a delete symbol. There are 3 · such as the scope of patents! The general-purpose extendable object:::----the interface-only architecture of read-only memory space efficiency = 'where the library device is - random access memory memory with two-swept memory and A hard disk is one of its orders.隹 326 传利利(补件)\95-05\TF954507 (such as the application for patent scope) in the general extension (4) interface / 16 1307838 extended initial interface interface must be > The use of Wei Weiyi space under the wood structure:: where the driver or data is the driver of the program +, the driver of the additional function; = at least one of the regenerated data, etc. The scope of the read-only memory space usage efficiency under the framework of the extension of the _ _ _ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = In the section, the _ρΕι and/or DXE program section is divided in the read-only memory, and the pEI and/or DXE program section has a new section mark, the size of the section, and the size of the data body section. And pointing to one of the indicators of the data body section and other information. 326\ patent specification (supplement)\95-05\TF954507 17