CN104572166A - UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Feiteng desk computer - Google Patents
UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Feiteng desk computer Download PDFInfo
- Publication number
- CN104572166A CN104572166A CN201410112114.5A CN201410112114A CN104572166A CN 104572166 A CN104572166 A CN 104572166A CN 201410112114 A CN201410112114 A CN 201410112114A CN 104572166 A CN104572166 A CN 104572166A
- Authority
- CN
- China
- Prior art keywords
- firmware
- module
- uefi
- internal memory
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Abstract
The invention relates to a UEFI (Unified Extensible Firmware Interface) firmware implementation method based on a Feiteng desk computer, and belongs to the technical field of computer firmware. Firmware is divided into a hardware abstraction layer, a firmware core layer, an equipment protocol layer and a firmware application layer, wherein the hardware abstraction layer is used for realizing the initialization of key hardware components such as a processor, an internal memory and a chipset, packaging and abstracting other board-level hardware and realizing the initialization, and also providing a function interface for accessing bottom-layer hardware equipment for an upper module; the firmware core layer is used for establishing a system service table in a UEFI to carry out the unified management of all modules in the firmware and the management of various resources; the equipment protocol layer is used for realizing various standard industrial specifications; the firmware application layer is used for realizing all functions of the firmware, such as interface configuration, system monitoring, file system and operating system guiding. The UEFI firmware implementation method can realize firmware products, with high expandability and perfect functions, meeting international mainstream UEFI firmware specifications on the Feiteng desk computer so as to support the normal start and operation of the Feiteng desk computer.
Description
Technical field
The invention belongs to computer firmware technical field, relate to a kind of implementation method based on the UEFI firmware of Feiteng processor desk side computer system (hereinafter referred to as desktop computer of soaring).
Background technology
UEFI (Unified Extensible Firmware Interface, unified Extensible Firmware Interface) is the interface specification of a kind of computer firmware (or being called BIOS), is also the topmost industrial standard about firmware.UEFI specification is carry out formulating towards the Itanium of Intel Company and X 86 processor at first, but UEFI specification itself has nothing to do with processor architecture, is applied to the processor platforms such as X86, Itanium, ARM at present.The computer firmware (hereinafter referred to as UEFI firmware) meeting UEFI specification has lot of superiority relative to traditional firmware, and the X86 business computer system of current main flow is all have employed UEFI firmware substantially.
Soaring is the domestic general central processor developed by the National University of Defense Technology, adopts SPARC reduced instruction set computer framework, achieves multi-core, multithreading, support hardware Intel Virtualization Technology.Feiteng processor has formed many moneys type product, can be applicable to desk-top, portable computer and server product.The Feiteng processor being applied to desk-top computer product at present mainly FT1000A, FT1000A is a SOC, not only comprises processor core, is also integrated with multiple peripheral control unit.
OBP (Open Boot PROM) is the firmware on Feiteng processor platform, is at first to be proposed in 1989 by SUN company.OBP meets IEEE1275 standard, primary responsibility Feiteng processor platform power-on self-test, platform initialization and guiding operating system.Because Feiteng processor support hardware is virtual, so first run a monitor of virtual machine Hypervisor when system electrification, realize the virtual and hardware resource management of hardware resource by Hypervisor, then control is given and start firmware OBP.Compared with UEFI firmware, OBP exists a lot of not enough, and be mainly manifested in: OBP Forth writes, Forth language is unexpected winner language, and the developer grasping this language is little, causes development difficulty very large, safeguards also very difficult; OBP is that the Open Source Code provided based on SUN company is developed, and uses the company of OBP little, lacks the extensive support of industrial chain; It is that the peripheral hardware that Forth language is write is supported that OBP only carries driving to plate, is difficult to the peripheral hardware supporting main flow.
Summary of the invention
Object of the present invention, mainly in order to solve the defect of above-mentioned prior art, provides a kind of implementation method of the UEFI firmware based on desk-top computer of soaring.According to this method, desktop computer can realize out meet that international mainstream UEFI firmware specification, extensibility are strong, the fastener product of perfect in shape and function soaring, and OBP can be substituted completely, with the normal start-up and operation of desktop computer of supporting to soar.
Based on an implementation method for the UEFI firmware of desktop computer of soaring, firmware is divided into hardware abstraction layer, firmware core layer, device protocol layer and firmware application layer.
Wherein, hardware abstraction layer realizes the initialization of the key hardware components such as processor, internal memory, peripheral control unit, carries out packaging and abstract and realize initialization, simultaneously for upper layer module provides the function interface of access bottom hardware equipment to other plate level hardware.It comprises processor driver module and peripheral hardware driver module, and processor driver module completes the initial work of processor, internal memory, and provides the interface of access processor and internal memory; The mainly driving of various peripheral hardware on mainboard of peripheral hardware driver module, as video card, hard disk, keyboard, USB device, network interface card etc., each peripheral hardware can corresponding (or multiple) driver module.For the hardware platform based on FT1000A, peripheral hardware driver module also will complete initialization and the Resourse Distribute work of peripheral control unit integrated in processor.
Firmware core layer is similar to the kernel of operating system, sets up the system service table in UEFI, carries out the unified management of all modules in firmware and the management of various resource.It comprises firmware core loading module, firmware nucleus module and architecture functional module, firmware core loading module is responsible for loading firmware nucleus module, and prepare running environment for it, service (Runtime Service) table when firmware nucleus module is responsible for setting up the startup service (Boot Service) in UEFI specification and runs, load, run other functional modules, what manage between each module is mutual, realize the management of internal memory, realize and safeguard tick interrupt and case mechanism, realize and safeguard the level of privilege mechanism of firmware application, realize the administrative mechanism of the Protocol defined in UEFI specification, realize other Mechanism and FunctionsDNAs that UEFI code requirement realizes, as debugging interface, compression algorithm, variable storage/process etc.Architectural Protocol in architecture Implement of Function Module UEFI specification, comprises multiple functional module, and each module realizes an Architectural Protocol.Each Architectural Protocol comprises some infrastructure service interfaces, calls for other functional modules in firmware.
Device protocol layer realizes the industrial specification of various standard, comprises bus protocol, Peripheral Interface etc.It comprises bus protocol module, realizes various bus protocol, as PCI/PCIE, SATA, PATA, SCSI, USB, ISA, SMBUS, LPCBUS etc.Normally a module realizes a kind of bus protocol, and passes through the interface of Protocol mechanism " issue " these buses in UEFI specification, and other modules just can use these interfaces to visit bus like this.
Firmware application layer realizes the various functions of firmware, as configuration interface, system monitoring, file system, booting operating system etc.; It comprises device scan module, human-computer interface module, system-monitoring module, IEEE1275 support module, system startup module, kernel loads module and Shell module, device scan module enumerates all external units in system, as the equipment in PCI/PCIE bus, for these equipment Resources allocation, and equipment and corresponding peripheral hardware driver module are carried out Connect (also namely giving this device drives to manage); Human-computer interface module is positioned on video driver module, realizes the interface that all displays are relevant, as arranged display mode, at ad-hoc location printable character string, Show Picture, cls etc.; The real-time check processing actuator temperature of system-monitoring module, system voltage and rotation speed of the fan, adjust the rotating speed of fan according to temperature value, allow user's design temperature threshold value, when temperature is too high, carry out automatic shutdown; IEEE1275 support module realizes function interface, the data structure of firmware and the operating system defined in IEEE1275 specification, calls in the start-up and operation stage for operating system; System starts module provides patterned user's configuration interface, and user, by the mode of menu operation, checks system information and is configured system.Finally according to the selection of user, start the operating system from memory device; File system module realizes FAT/FAT32, EXT2/3/4 and ISO9660 file system, supports the read operation to file; The final stage that kernel loads module starts in system, kernel file (or kernel loads device) is loaded in internal memory by this module from the storage mediums such as hard disk, USB flash disk, CD, and prepare necessary parameter for kernel file, then the entrance jumping to kernel (or kernel loads device) performs, and has so just given operating system by control; Shell module Shell is the command line environment that UEFI firmware provides, and based on a large amount of interface service provided in UEFI firmware, can develop the multiple firmware application programs under Shell.
The carrying out practically step of the UEFI firmware based on desktop computer of soaring of the present invention is as follows:
(1) initialization processor, internal memory, sets up the Essential Environment that firmware runs;
(2) UEFI firmware code is copied to internal memory, and decompress(ion) is carried out to firmware, loading firmware nucleus module;
(3) infrastructure service of UEFI firmware is set up;
(4) load UEFI firmware functional module, comprise architecture functional module, device protocol module;
(5) scanning device is also equipment distributing system resource, loading equipemtn driver module, finishing equipment initialization;
(6) load and execution firmware application module;
(7) configuration interface is run;
(8) from memory device load operation system.
In above-mentioned steps, in step (1), perform processor driver module.Before step (1) performs, monitor of virtual machine Hypervisor in system has achieved the initialization of concurrent physical processor and internal memory, now processor driver module only needs to carry out initialization to virtual processor, internal memory, carry out the configuration of parameter, and the interface of the parts such as access CPU, Cache, internal memory is provided.
In above-mentioned steps, in step (2), perform firmware core loading module.After step (1) is complete, Installed System Memory initialization is good, and now firmware code can run to accelerate travelling speed in internal memory; And firmware code can be realized by C language, Speeding up development speed.The functional module comprised in firmware is more, and the finite capacity of FLASH chip, generally need the firmware volume depositing functional module to compress, firmware core loading module is responsible for the firmware volume of compression being copied in internal memory from FLASH, and carries out decompress(ion); After decompress(ion) success, in internal memory, create HOB (Hand-Off Block) tables of data, deposit the system informations such as processor, internal memory, FLASH, be supplied to follow-up firmware module and use; Finally, control is given firmware nucleus module by firmware core loading module.
In above-mentioned steps, in step (3), perform firmware nucleus module.The system service of firmware nucleus module first initialization UEFI, for follow-up functional module loading, run and prepare.Mainly complete the initialization of agent list when UEFI system table, UEFI startup agent list and UEFI run, specific service comprises code debugging, memory management, the management of UEFI mirror image, HOB, UEFI clock, FLASH access, decompression, firmware volume parsing, UEFI event, task priority, UEFI Protocol management, UEFI variable access etc.System service table leaves the specific region of internal memory in, and all functions module in UEFI firmware can call these system services.
In above-mentioned steps, the functional module of firmware nucleus module loading firmware in step (4).Firmware nucleus module, by retrieval firmware volume, is searched functional module wherein successively, and is loaded in internal memory.Each functional module is compiled into the performed mirror image of a PE/ELF form, and firmware nucleus module needs analytical capabilities module mirror image, is then loaded into the particular address place of internal memory, and jumps to entrance function.After the entrance function of functional module is complete, usually can turn back to firmware nucleus module, firmware nucleus module proceeds the loading of next functional module.
The module be loaded in step (4) comprises architecture functional module, device protocol module.Wherein, architecture functional module major function is the Architectural Protocol realized in UEFI specification, mainly comprise: Boot Device Selection (BDS), CPU, Metronome, Monotonic Counter, Real TimeClock, Runtime, Security, Status Code, Timer, Variable, Variable Write, WatchdogTimer, each Architectural Protocol is realized by a module; Device protocol layer module mainly realizes the function interface of accessing the buses such as PCI/PCIE, SATA, PATA, SCSI, USB, ISA, SMBUS, LPCBUS, and be encapsulated in Protocol and call for other functional modules, normally a module realizes a kind of bus protocol.
In above-mentioned steps, the initialization of finishing equipment in step (5).Firmware nucleus module loading equipemtn driver module, realize the initialization of peripheral hardware on mainboard and realize the function interface of access peripheral hardware, comprising north and south bridge chip, video card, SATA/IDE controller, USB controller, SMBUS controller, LPC controller, keyboard, network interface card etc.Usually a kind of device drives is realized by a module.In addition, in this stage by all peripheral hardwares in device scan module scans system, and be peripheral assignment internal memory, IO and interrupt resources, such peripheral hardware could normally work under an operating system.
In above-mentioned steps, the firmware application module in step (6) in firmware nucleus module loading firmware volume, and realize corresponding firmware function.Comprise display module, system-monitoring module, IEEE1275 support module, file system module, kernel loads module, Shell module, system startup module.Finally, control is given system and is started module by firmware nucleus module, prepares to start the operating system.
In above-mentioned steps, in step (7), system starts the service interface that module provides by calling firmware nucleus module and other functional modules, demonstrates figure configuration interface as human-computer interaction interface.In this stage, firmware carries out next step work according to the operation of user, comprises and provides the display of system information and the configuration of systematic parameter, and the equipment that selection will start, and comprises hard disk, CD, USB flash disk, order line etc.User exits configuration interface by specific keys and enters into next execution step.
In above-mentioned steps, in step (8), realize the startup of operating system.According to user configured boot sequence, system starts module and attempts successively, from media such as hard disk, CD, USB flash disks, operating system nucleus file (or kernel loads device) is loaded into internal memory, and prepare necessary start-up parameter for kernel, then control is given kernel (or kernel loads device), thus the startup work of completion system.After os starting completes, the IEEE1275 interface and data structure that realize in firmware can be called.
Beneficial effect:
1, method of the present invention meets UEFI and the PI firmware specification of international mainstream, and the Open Source Code resource that UEFI alliance can be utilized to provide realizes firmware fast; A lot of peripheral hardware board manufacturer all provides the driving based on UEFI specification, also greatly can accelerate the progress of firmware development; Firmware layer can provide more device drives and abundant firmware function.In addition, the computer industry standard that the support of UEFI firmware is main, as ACPI (advanced configuration and the power-management interface) specification that current Feiteng processor is not also supported, the firmware adopting the present invention to design like this can increase the support to these specifications easily.
2, the important feature of the UEFI firmware of the present invention's design is high modularization, and the function that firmware will realize is broken down into a lot of subfunction, and each subfunction is realized by independent module, and loads and manage these functional modules by a nucleus module.Therefore the function of customized firmware easily can be carried out by additions and deletions module.
3, the UEFI firmware of the present invention's design can realize the support to main flow peripheral hardware, solves the defect of Feiteng processor platform tradition firmware OBP in the compatible support of peripheral hardware, brings benefit for the industrialization promoting Feiteng processor.
Accompanying drawing explanation
Fig. 1 is with the configuration diagram of part based on the UEFI of desktop computer of soaring.
Embodiment
To develop simultaneously embodiment below in conjunction with accompanying drawing, describe the present invention.
As accompanying drawing 1 represents, below for the desktop computer mainboard that a model designed by electric section of China 15 is CETC15-FT1000A-DESKTOP-V1.4, introduce the embodiment of the UEFI firmware that the present invention describes.Mainly comprise the following steps:
(1) realize the functional module in STU stage, comprise two modules, these two modules will be placed to the starting position of FLASH chip successively after compiling, and are performed successively upon power-up of the system.Comprise:
(1.1) a Start module, i.e. processor driver module is created.The initialization such as processor, Cache (high-speed cache), internal memory, address window, TLB (bypass conversion buffered) are realized according to FT1000A processor handbook of soaring, realize the initialization of MCU (Memory Controller Hub), SMBUS and internal memory, and the interface of the parts such as access CPU, Cache, internal memory is provided;
(1.2) a Sec module is created.The function of the realization of this module is included in internal memory and creates the data structure that some deposit processor, memory information, unzips in internal memory by the functional module in FLASH chip, last load and execution firmware nucleus module DxeCore.
(2) firmware nucleus module DxeCore is realized.The function realized mainly comprises: agent list when realizing the startup service that defines in UEFI specification and run, load, run other functional modules, what manage between each module is mutual, realize the management of internal memory, realize and safeguard tick interrupt and case mechanism, realizing and safeguard the level of privilege mechanism of firmware application, realize the administrative mechanism of the Protocol defined in UEFI specification, optimized integration function library, and debugging interface, compression algorithm, variable storage/process etc.
(3) realize Architectural Protocol, comprise Variable, Variable Write, Timer, CPU, Metronome, Monotonic Counter, Status Code, Watchdog Timer, RTC, BDS.A module realizes a kind of Architectural Protocol.
(4) peripheral hardware driver module is realized.Comprise:
(4.1) driver module of chipset is realized.Initialization to AMD RS780 north bridge chips, AMD SB710 South Bridge chip is realized according to chipset handbook, and the initialization of pci bus, USB, SATA/IDE, LPC/SMBUS bus, HD Audio controller in South Bridge chip.
(4.2) realize peripheral hardware driver module, comprise video driver, USB storage device driving, the driving of PS2 keyboard drive, USB keyboard drive, SATA device drives, IDE device drives, trawl performance, tick interrupt.
(4.3) realize peripheral hardware enumeration module, enumerate the equipment in PCI/PCIE bus, and be equipment distribution IO, internal memory and interrupt resources.
(5) realize bus driver block, comprise PCI/PCIE, SATA, PATA, SCSI, USB, ISA, SMBUS, LPCBUS, a module realizes a kind of bus protocol.
(6) firmware application layer module is realized.Mainly comprise:
(6.1) graphical interfaces module is realized.A patterned configuration interface or command line environment can be realized, support that user checks processor model and frequency, memory size and frequency, system time, boot sequence, peripheral hardware list etc., and allow user to be configured system time, boot sequence.
(6.2) IEEE1275 support module is realized, according to IEEE Std.1275-1994 and IEEE Std.1275.1-1994 specification, set up os starting and the device tree (Device Tree) required for operation, realize CLIENT PROGRAM interface (Client Interface), equipment interface (Device Interface) etc.
(6.3) boot kernel module is realized, the operational factor that data structure needs with deposit operation system is created in internal memory, and according to the configuration of user, from the fixing sector of hard disk, USB flash disk, CD, read operation system kernel loader SILO (Sparc Improved boot LOader) is in internal memory, finally give SILO by control, by the loading of SILO complete operation system kernel.
(6.4) system that realizes starts module, and its function comprises: load configuration interface, call the loading of the Interface realization operating system in boot kernel module.
(6.5) Shell module is realized, user can start to Shell command line environment by arranging boot sequence in configuration interface, and Shell provides multiple order to realize file in the checking of system information, device parameter configuration, access storage media, equipment control and test, os starting etc.
In above-mentioned steps, for the module relevant to particular hardware platform, for mainly FT1000A processor this example, the user manual according to hardware or the Open Source Code with reference to producer is needed to develop; For the general module irrelevant with hardware platform, as DxeCore module, Architectural Protocol module, bus protocol, SATA/IDE device drives, USB storage device driving, keyboard drive, file system, BDS module etc., the module and code that provide in EDK II can be adopted; For the functional module of firmware, as configuration interface, operating system loading etc., need to develop according to real needs; For video driver, due to OPROM (the Option ROM on video card, the driving that video card producer provides) be x86 instruction set, the Feiteng processor of SPARC instruction set cannot perform, so adopt an X86 emulation module of increasing income to explain the OPROM performing video card in firmware, realize the initialization to video card.
In sum, these are only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (9)
1. based on a UEFI firmware implementation method for desk-top computer of soaring, it is characterized in that, firmware is divided into hardware abstraction layer, firmware core layer, device protocol layer and firmware application layer; Wherein, hardware abstraction layer realizes the initialization of the key hardware components such as processor, internal memory, peripheral control unit, packaging and abstract and realize initialization is carried out to other plate level hardware, simultaneously for upper layer module provides the function interface of access bottom hardware equipment, it comprises processor driver module and peripheral hardware driver module; Firmware core layer is similar to the kernel of operating system, sets up the system service table in UEFI, and carry out the unified management of all modules in firmware and the management of various resource, it comprises firmware core loading module, firmware nucleus module and architecture functional module; Device protocol layer realizes the industrial specification of various standard, comprises bus protocol, Peripheral Interface; It comprises bus protocol module, realizes various bus protocol; Firmware application layer realizes the various functions of firmware, as configuration interface, system monitoring, file system, booting operating system etc.; It comprises device scan module, human-computer interface module, system-monitoring module, IEEE1275 support module, system startup module, kernel loads module and Shell module; The carrying out practically step of I firmware is as follows:
(1) initialization processor, internal memory, sets up the Essential Environment that firmware runs;
(2) UEFI firmware code is copied to internal memory, and decompress(ion) is carried out to firmware, loading firmware nucleus module;
(3) infrastructure service of UEFI firmware is set up;
(4) load UEFI firmware functional module, comprise architecture functional module, device protocol module;
(5) scanning device is also equipment distributing system resource, loading equipemtn driver module, finishing equipment initialization;
(6) load and execution firmware application module;
(7) configuration interface is run;
(8) from memory device load operation system.
2. as claimed in claim 1 based on the UEFI firmware implementation method of desk-top computer of soaring, it is characterized in that, in described step (1), perform processor driver module; Before step (1) performs, monitor of virtual machine Hypervisor in system has achieved the initialization of concurrent physical processor and internal memory, now processor driver module only needs to carry out initialization to virtual processor, internal memory, carry out the configuration of parameter, and the interface of the parts such as access CPU, Cache, internal memory is provided.
3. as claimed in claim 1 based on the UEFI firmware implementation method of desk-top computer of soaring, it is characterized in that, in described step (2), perform firmware core loading module; After step (1) is complete, Installed System Memory initialization is good, and now firmware code can run to accelerate travelling speed in internal memory; And firmware code can be realized by C language, Speeding up development speed.The functional module comprised in firmware is more, and the finite capacity of FLASH chip, generally need the firmware volume depositing functional module to compress, firmware core loading module is responsible for the firmware volume of compression being copied in internal memory from FLASH, and carries out decompress(ion); After decompress(ion) success, in internal memory, create HOB (Hand-Off Block) tables of data, deposit the system informations such as processor, internal memory, FLASH, be supplied to follow-up firmware module and use; Finally, control is given firmware nucleus module by firmware core loading module.
4. as claimed in claim 1 based on the UEFI firmware implementation method of desk-top computer of soaring, it is characterized in that, in described step (3), perform firmware nucleus module.The system service of firmware nucleus module first initialization UEFI, for follow-up functional module loading, run and prepare.Mainly complete the initialization of agent list when UEFI system table, UEFI startup agent list and UEFI run, specific service comprises code debugging, memory management, the management of UEFI mirror image, HOB, UEFI clock, FLASH access, decompression, firmware volume parsing, UEFI event, task priority, UEFI Protocol management, UEFI variable access etc.System service table leaves the specific region of internal memory in, and all functions module in UEFI firmware can call these system services.
5. as claimed in claim 1 based on the UEFI firmware implementation method of desk-top computer of soaring, it is characterized in that, the functional module of firmware nucleus module loading firmware in described step (4); Firmware nucleus module, by retrieval firmware volume, is searched functional module wherein successively, and is loaded in internal memory; Each functional module is compiled into the performed mirror image of a PE/ELF form, and firmware nucleus module needs analytical capabilities module mirror image, is then loaded into the particular address place of internal memory, and jumps to entrance function.After the entrance function of functional module is complete, usually can turn back to firmware nucleus module, firmware nucleus module proceeds the loading of next functional module.
6. as claimed in claim 1 based on the UEFI firmware implementation method of desk-top computer of soaring, it is characterized in that, the initialization of finishing equipment in described step (5); Firmware nucleus module loading equipemtn driver module, realize the initialization of peripheral hardware on mainboard and realize the function interface of access peripheral hardware, comprising north and south bridge chip, video card, SATA/IDE controller, USB controller, SMBUS controller, LPC controller, keyboard, network interface card etc.Usually a kind of device drives is realized by a module.In addition, in this stage by all peripheral hardwares in device scan module scans system, and be peripheral assignment internal memory, IO and interrupt resources, such peripheral hardware could normally work under an operating system.
7. as claimed in claim 1 based on the UEFI firmware implementation method of desk-top computer of soaring, it is characterized in that, the firmware application module in described step (6) in firmware nucleus module loading firmware volume, and realize corresponding firmware function; Comprise display module, system-monitoring module, IEEE1275 support module, file system module, kernel loads module, Shell module, system startup module.Finally, control is given system and is started module by firmware nucleus module, prepares to start the operating system.
8. as claimed in claim 1 based on the UEFI firmware implementation method of desk-top computer of soaring, it is characterized in that, in described step (7), system starts the service interface that module provides by calling firmware nucleus module and other functional modules, demonstrates figure configuration interface as human-computer interaction interface; In this stage, firmware carries out next step work according to the operation of user, comprises and provides the display of system information and the configuration of systematic parameter, and the equipment that selection will start, and comprises hard disk, CD, USB flash disk, order line etc.User exits configuration interface by specific keys and enters into next execution step.
9., as claimed in claim 1 based on the UEFI firmware implementation method of desk-top computer of soaring, it is characterized in that, in described step (8), realize the startup of operating system.According to user configured boot sequence, system starts module and attempts successively, from media such as hard disk, CD, USB flash disks, operating system nucleus file (or kernel loads device) is loaded into internal memory, and prepare necessary start-up parameter for kernel, then control is given kernel (or kernel loads device), thus the startup work of completion system.After os starting completes, the IEEE1275 interface and data structure that realize in firmware can be called.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410112114.5A CN104572166A (en) | 2014-03-21 | 2014-03-21 | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Feiteng desk computer |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410112114.5A CN104572166A (en) | 2014-03-21 | 2014-03-21 | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Feiteng desk computer |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104572166A true CN104572166A (en) | 2015-04-29 |
Family
ID=53088328
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410112114.5A Pending CN104572166A (en) | 2014-03-21 | 2014-03-21 | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Feiteng desk computer |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104572166A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106354498A (en) * | 2016-08-25 | 2017-01-25 | 睿芯信息科技（上海）有限公司 | Linux system equipment loading method |
| CN106909351A (en) * | 2015-12-22 | 2017-06-30 | 中电科技（北京）有限公司 | A kind of implementation method of the EXT file system based on UEFI firmwares |
| CN110618876A (en) * | 2019-03-21 | 2019-12-27 | 天津麒麟信息技术有限公司 | Linux and Android coexistence and interaction method based on Feiteng platform and shared kernel |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101430642A (en) * | 2007-11-09 | 2009-05-13 | 中国长城计算机深圳股份有限公司 | Method and system for implementing operation interface used for UEFI |
| US20120023318A1 (en) * | 2010-07-22 | 2012-01-26 | Xing Bin C | Providing platform independent memory logic |
| US20120159204A1 (en) * | 2010-12-21 | 2012-06-21 | Di Tang | System and method for power management |
| CN103176915A (en) * | 2013-03-28 | 2013-06-26 | 华为技术有限公司 | Method and device of managing internal memory |
| CN103207797A (en) * | 2013-03-15 | 2013-07-17 | 南京工业大学 | Capsule type custom-made updating method based on unified extensible firmware interface firmware system |
-
2014
- 2014-03-21 CN CN201410112114.5A patent/CN104572166A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101430642A (en) * | 2007-11-09 | 2009-05-13 | 中国长城计算机深圳股份有限公司 | Method and system for implementing operation interface used for UEFI |
| US20120023318A1 (en) * | 2010-07-22 | 2012-01-26 | Xing Bin C | Providing platform independent memory logic |
| US20120159204A1 (en) * | 2010-12-21 | 2012-06-21 | Di Tang | System and method for power management |
| CN103207797A (en) * | 2013-03-15 | 2013-07-17 | 南京工业大学 | Capsule type custom-made updating method based on unified extensible firmware interface firmware system |
| CN103176915A (en) * | 2013-03-28 | 2013-06-26 | 华为技术有限公司 | Method and device of managing internal memory |
Non-Patent Citations (1)
| Title |
|---|
| 杜振龙 等: "MIPS架构计算机平台的支持固件研究", 《兰州理工大学学报》 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106909351A (en) * | 2015-12-22 | 2017-06-30 | 中电科技（北京）有限公司 | A kind of implementation method of the EXT file system based on UEFI firmwares |
| CN106909351B (en) * | 2015-12-22 | 2021-04-20 | 中电科技（北京）有限公司 | UEFI (unified extensible firmware interface) firmware-based EXT (extensible firmware interface) file system implementation method |
| CN106354498A (en) * | 2016-08-25 | 2017-01-25 | 睿芯信息科技（上海）有限公司 | Linux system equipment loading method |
| CN106354498B (en) * | 2016-08-25 | 2020-05-08 | 睿芯信息科技（上海）有限公司 | Method for loading equipment in Linux system |
| CN110618876A (en) * | 2019-03-21 | 2019-12-27 | 天津麒麟信息技术有限公司 | Linux and Android coexistence and interaction method based on Feiteng platform and shared kernel |
| CN110618876B (en) * | 2019-03-21 | 2023-05-23 | 麒麟软件有限公司 | Linux and Android coexistence and interaction method based on Feiteng platform and shared kernel |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104572165B (en) | A kind of UEFI firmware implementation methods based on FT server | |
| CN104572164A (en) | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Feiteng portable computer | |
| CN104572061A (en) | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Loongson server | |
| CN104572161B (en) | A kind of UEFI firmware implementation methods based on Godson portable computer | |
| US9880867B2 (en) | Method and subsystem for data exchange between a guest operating system and a virtualization layer | |
| CN106445576B (en) | Motherboard and its computer implemented method and the readable storage device of non-transient computer | |
| US20100262722A1 (en) | Dynamic Assignment of Graphics Processing Unit to a Virtual Machine | |
| US10725770B2 (en) | Hot-swapping operating systems using inter-partition application migration | |
| CN104572163A (en) | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Loongson desk computer | |
| US20140181811A1 (en) | Hypervisor modification of advanced configuration and power interface (acpi) tables | |
| CN106909399A (en) | A kind of UEFI firmware implementation methods based on server computer | |
| CN106909349A (en) | A kind of UEFI firmware implementation methods based on server | |
| CN104572162A (en) | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Loongson handheld computer | |
| US20130159689A1 (en) | Method and apparatus for initializing embedded device | |
| CN106909400A (en) | A kind of UEFI firmware implementation methods based on notebook | |
| CN104572166A (en) | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Feiteng desk computer | |
| CN106909346A (en) | A kind of UEFI firmware implementation methods based on integrated computer | |
| CN106909345A (en) | A kind of UEFI firmware implementation methods based on desktop computer | |
| CN106909347A (en) | A kind of UEFI firmware implementation methods of portable computer | |
| Fornaeus | Device hypervisors | |
| Campbell et al. | An introduction to virtualization | |
| Bose et al. | Benchmarking database performance in a virtual environment | |
| CN104182271A (en) | Virtualization implementation method based on SW processor | |
| CN101982814B (en) | Paging instruction for a virtualization engine to local storage | |
| CN100346301C (en) | Method for normal running self-testing phase in early starting up period |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20150429 |
|
| WD01 | Invention patent application deemed withdrawn after publication |