CN112433772A - Method and terminal for embedded uboot recognition starting of file system - Google Patents
Method and terminal for embedded uboot recognition starting of file system Download PDFInfo
- Publication number
- CN112433772A CN112433772A CN202011451034.4A CN202011451034A CN112433772A CN 112433772 A CN112433772 A CN 112433772A CN 202011451034 A CN202011451034 A CN 202011451034A CN 112433772 A CN112433772 A CN 112433772A
- Authority
- CN
- China
- Prior art keywords
- starting
- image
- partition
- mirror image
- file system
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4406—Loading of operating system
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method and a terminal for identifying and starting a file system by an embedded uboot; the method comprises the steps of starting uboot and starting a preset starting menu; reading a starting mirror image in each partition, setting the starting mirror image as each starting option under the starting menu, and configuring a corresponding starting environment variable for each starting option according to the type of the starting mirror image; receiving selection information of a user, and starting a file system according to a selected starting option in the selection information and the starting environment variable corresponding to the selected starting option; when the uboot minimum system is used for starting the file system and the plurality of file systems are provided, automatic identification can be realized for selection, smooth starting of the system is ensured, and services on the embedded equipment can run normally; and complicated setting is not needed manually, and the file system can be conveniently started by inexperienced personnel of the uboot.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a terminal for identifying and starting a file system by an embedded uboot.
Background
uboot is a small segment of program executed before the operating system runs, and through the small segment of program, hardware equipment can be initialized, a mapping table of a memory space is established, so that a proper system software and hardware environment is established, and preparation is made for finally calling an operating system kernel. Meaning that if we want an os to run on our board we must first perform some basic configuration and initialization on our board before we can boot the os into operation.
In the existing embedded system, when uboot is started, the environment variable of uboot needs to specify the partition where the device tree image, the kernel image and the file system are located first, and if the file system is replaced or the image position is changed, the system can not be started.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: the method and the terminal for identifying and starting the file system by the embedded uboot can automatically identify the file system and ensure the smooth starting of the file system.
In order to solve the technical problems, the invention adopts the technical scheme that:
a method for starting a file system by embedded uboot recognition comprises the following steps:
s1, starting the uboot and starting a preset starting menu;
s2, reading the starting mirror image in each partition, setting the starting mirror image as each starting option under the starting menu, and configuring a corresponding starting environment variable for each starting option according to the type of the starting mirror image;
s3, receiving selection information of a user, and starting the file system according to the selected starting option in the selection information and the starting environment variable corresponding to the selected starting option.
In order to solve the technical problem, the invention adopts another technical scheme as follows:
an embedded uboot recognition starting file system terminal, comprising a processor, a memory and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the computer program to realize the following steps:
s1, starting the uboot and starting a preset starting menu;
s2, reading the starting mirror image in each partition, setting the starting mirror image as each starting option under the starting menu, and configuring a corresponding starting environment variable for each starting option according to the type of the starting mirror image;
s3, receiving selection information of a user, and starting the file system according to the selected starting option in the selection information and the starting environment variable corresponding to the selected starting option.
The invention has the beneficial effects that: when the uboot minimum system is used for starting the file system and the plurality of file systems are provided, automatic identification can be realized for selection, smooth starting of the system is ensured, and services on the embedded equipment can run normally; and complicated setting is not needed manually, and the file system can be conveniently started by inexperienced personnel of the uboot.
Drawings
FIG. 1 is a flowchart of a method for embedded uboot recognition to start a file system according to an embodiment of the present invention;
fig. 2 is a structural diagram of a terminal for identifying and starting a file system by an embedded uboot according to an embodiment of the present invention;
FIG. 3 is a detailed flowchart of a method for starting a file system by embedded uboot recognition according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a startup menu of a method for embedded uboot recognition to start a file system according to an embodiment of the present invention;
FIG. 5 is a reference diagram of the steps specified in a method for embedded uboot recognition booting a file system according to an embodiment of the present invention;
description of reference numerals:
1. a terminal for starting a file system is identified by an embedded uboot; 2. a processor; 3. a memory.
Detailed Description
In order to explain technical contents, achieved objects, and effects of the present invention in detail, the following description is made with reference to the accompanying drawings in combination with the embodiments.
Referring to fig. 1 and fig. 3, a method for starting a file system by embedded uboot recognition includes:
s1, starting the uboot and starting a preset starting menu;
s2, reading the starting mirror image in each partition, setting the starting mirror image as each starting option under the starting menu, and configuring a corresponding starting environment variable for each starting option according to the type of the starting mirror image;
s3, receiving selection information of a user, and starting the file system according to the selected starting option in the selection information and the starting environment variable corresponding to the selected starting option.
From the above description, the beneficial effects of the present invention are: when the uboot minimum system is used for starting the file system and the plurality of file systems are provided, automatic identification can be realized for selection, smooth starting of the system is ensured, and services on the embedded equipment can run normally; and complicated setting is not needed manually, and the file system can be conveniently started by inexperienced personnel of the uboot.
Further, the step S1 is specifically:
and starting the uboot, reading the partition number of the storage equipment, judging whether the partition number is greater than 1, and if the partition number is greater than 1, starting a preset starting menu.
According to the description, the number of the partitions of the storage device is judged to preliminarily judge the number of the file systems, whether the starting menu is started or not is further determined, and the function of starting the menu is started only when the number of the file systems is larger than 1, so that the method is more humanized.
Further, in step S2, the boot image includes a ramdisk image and a kernel image.
As can be seen from the above description, the image types include ramdisk image and kernel image, and different image types will subsequently provide different operations, which is more applicable.
Further, step S2 is specifically:
traversing files in each partition, judging whether the type of the starting mirror image in the partition is the ramdisk mirror image, if so, taking the starting mirror image as one starting option under the starting menu, and setting the name of the ramdisk mirror image as the starting environment variable of the corresponding starting option;
if the current partition is the kernel image mirror image, continuously traversing the files in the current partition, judging whether an init file necessary for starting a file system exists in the current partition, if the init file exists, taking the kernel image mirror image as a starting option under the starting menu, and setting the name of the kernel image mirror image and the partition where the init file is located as the starting environment variable corresponding to the starting option.
According to the description, under the condition that the starting menu is started, different settings are carried out on the starting environment variable according to different mirror image types, the pertinence is stronger, no manual operation is needed, and the starting menu is more convenient.
Further, if the number of divisions is 1 in step S1, the process proceeds to step S4:
s4, traversing files in the partition, judging the type of the boot image, if the type of the boot image is the ramdisk image, setting the image name as the boot environment variable, and booting a file system;
otherwise, the type of the starting mirror image is the kernel image mirror image, files in the partition are continuously traversed, whether an init file necessary for starting the file system exists in the current partition is judged, if the init file exists, the name of the kernel image mirror image and the partition where the init file is located are set as the starting environment variable, the file system is started, and otherwise, the starting fails.
As can be seen from the above description, if the number of partitions is 1, only one file system is provided, and the boot menu does not need to be started, the boot image is directly read and operated according to the type of the boot image, which is faster and more convenient.
Referring to fig. 2, a terminal for starting a file system by embedded uboot identification includes a processor, a memory, and a computer program stored in the memory and running on the processor, where the processor executes the computer program to implement the following steps:
s1, starting the uboot and starting a preset starting menu;
s2, reading the starting mirror image in each partition, setting the starting mirror image as each starting option under the starting menu, and configuring a corresponding starting environment variable for each starting option according to the type of the starting mirror image;
s3, receiving selection information of a user, and starting the file system according to the selected starting option in the selection information and the starting environment variable corresponding to the selected starting option.
From the above description, the beneficial effects of the present invention are: when the uboot minimum system is used for starting the file system and the plurality of file systems are provided, automatic identification can be realized for selection, smooth starting of the system is ensured, and services on the embedded equipment can run normally; and complicated setting is not needed manually, and the file system can be conveniently started by inexperienced personnel of the uboot.
Further, the step S1 is specifically:
and starting the uboot, reading the partition number of the storage equipment, judging whether the partition number is greater than 1, and if the partition number is greater than 1, starting a preset starting menu.
According to the description, the number of the partitions of the storage device is judged to preliminarily judge the number of the file systems, whether the starting menu is started or not is further determined, and the function of starting the menu is started only when the number of the file systems is larger than 1, so that the method is more humanized.
Further, in step S2, the boot image includes a ramdisk image and a kernel image.
As can be seen from the above description, the image types include ramdisk image and kernel image, and different image types will subsequently provide different operations, which is more applicable.
Further, step S2 is specifically:
traversing files in each partition, judging whether the type of the starting mirror image in the partition is the ramdisk mirror image, if so, taking the starting mirror image as one starting option under the starting menu, and setting the name of the ramdisk mirror image as the starting environment variable of the corresponding starting option;
if the current partition is the kernel image mirror image, continuously traversing the files in the current partition, judging whether an init file necessary for starting a file system exists in the current partition, if the init file exists, taking the kernel image mirror image as a starting option under the starting menu, and setting the name of the kernel image mirror image and the partition where the init file is located as the starting environment variable corresponding to the starting option.
According to the description, under the condition that the starting menu is started, different settings are carried out on the starting environment variable according to different mirror image types, the pertinence is stronger, no manual operation is needed, and the starting menu is more convenient.
Further, when the processor executes the computer program, if the number of partitions is 1 in step S1, the process proceeds to step S4:
s4, traversing files in the partition, judging the type of the boot image, if the type of the boot image is the ramdisk image, setting the image name as the boot environment variable, and booting a file system;
otherwise, the type of the starting mirror image is the kernel image mirror image, files in the partition are continuously traversed, whether an init file necessary for starting the file system exists in the current partition is judged, if the init file exists, the name of the kernel image mirror image and the partition where the init file is located are set as the starting environment variable, the file system is started, and otherwise, the starting fails.
As can be seen from the above description, if the number of partitions is 1, only one file system is provided, and the boot menu does not need to be started, the boot image is directly read and operated according to the type of the boot image, which is faster and more convenient.
Referring to fig. 1, fig. 3, fig. 4 and fig. 5, a first embodiment of the present invention is:
a method for starting a file system by embedded uboot recognition comprises the following steps:
s1, starting the uboot and starting a preset starting menu;
wherein, the step S1 specifically includes:
starting the uboot, reading the partition number of the storage equipment, judging whether the partition number is greater than 1, and if the partition number is greater than 1, starting a preset starting menu;
in this embodiment, after the device is powered on, the start of the uboot is divided into two stages, i.e., the start of the uboot is divided into two stages. The first stage is as follows: setting an abnormal vector table, setting an ARM core as an svc mode, turning off a cache and an mmu, turning off a watchdog, initializing a clock, a serial port, a memory, initializing a stack space and clearing bss. The first stage is a conventional step, and the present embodiment is mainly the second stage content. And a second stage: reading the number and the format of the partitions on the storage device, judging whether the number of the partitions is more than 1, if so, starting bootmenu, and if the number of the partitions is 1, not starting bootmenu. The bootmenu in this embodiment is the start menu.
S2, reading the starting mirror image in each partition, setting the starting mirror image as each starting option under the starting menu, and configuring a corresponding starting environment variable for each starting option according to the type of the starting mirror image;
wherein, the boot image in step S2 includes a ramdisk image and a kernel image;
in this embodiment, step S2 specifically includes:
traversing files in each partition, judging whether the type of the starting mirror image in the partition is the ramdisk mirror image, if so, taking the starting mirror image as one starting option under the starting menu, and setting the name of the ramdisk mirror image as the starting environment variable of the corresponding starting option;
if the current partition is the kernel image mirror image, continuously traversing the files in the current partition, judging whether an init file necessary for starting a file system exists in the current partition, if the init file exists, taking the kernel image mirror image as a starting option under the starting menu, and setting the name of the kernel image mirror image and the partition where the init file is located as the starting environment variable corresponding to the starting option;
s3, receiving selection information of a user, and starting a file system according to the selected starting option in the selection information and the starting environment variable corresponding to the selected starting option;
if the number of divisions is 1 in step S1, the process proceeds to step S4:
s4, traversing files in the partition, judging the type of the boot image, if the type of the boot image is the ramdisk image, setting the image name as the boot environment variable, and booting a file system;
otherwise, the type of the starting mirror image is the kernel image mirror image, files in the partition are continuously traversed, whether an init file necessary for starting the file system exists in the current partition is judged, if the init file exists, the name of the kernel image mirror image and the partition where the init file is located are set as the starting environment variable, the file system is started, and otherwise, the starting fails.
In this embodiment, if bootmenu is started, the ramdisk mirror image and the kernel image mirror image in each partition are read, the file in each partition is traversed to determine whether the kernel mirror image is the ramdisk mirror image, and if not, the file system is continuously traversed to read the file system in the partition to start the necessary init file. Each bootable ramdisk mirror image and kernel image mirror image are used as boot options of bootmenu, as shown in fig. 4, if the bootable ramdisk mirror image is a ramdisk mirror image, the mirror image name is directly set as a boot environment variable, and if the bootable ramdisk mirror image is not a ramdisk mirror image, the kernel image name and the partition where the init file is located are set as the boot environment variable.
If only one ramdisk or kernel image mirror exists in the storage device, the name of the mirror and the partition where the kernel image mirror is located are directly set to the boot environment variable, as shown in fig. 5, specifically set to bootcmd.
For the subsequent start-up of the file system, no matter bootmenu or bootcmd, the specified kernel image and device tree (dtb) image are acquired. And setting a startup parameter in bootargs, mainly setting a root for specifying the position of rootfs, wherein the root is/dev/ram rw, a rootfstype which is commonly used, the option needs to be matched with the root for use, if the file system format is ext2, the option can be used in any case, but if the file system format is squashfs and jffs2, the file system type needs to be specified.
Starting the equipment, jumping to a kernel by the uboot, wherein the specific starting process of the kernel is as follows:
0. the cpu is set to svc mode, turning off the interrupt.
1. Prepare for decompression of the kernel (memory, interrupt, etc.).
2. Kernel self-decompression (vmlinux. lds).
3. Jump to entry address execution (head.s- > main.c) start _ kernel execution kernel.
4. Initialization of hardware (initial mm mmu interrupt (request _ irq), soft interrupt initialization, kernel timer) (parsing device tree, executing driver).
5. And mounting the root file system.
6. And starting a first user process init and executing the linux application program.
After the kernel is started, the kernel linux rc starts to call the inittab file, so as to obtain the behavior of the operating system and start to smoothly start the system.
Referring to fig. 2, the second embodiment of the present invention is:
an embedded uboot recognition starting file system terminal 1 comprises a processor 2, a memory 3 and a computer program which is stored on the memory 3 and can run on the processor 2, wherein the processor 2 realizes the steps in the first embodiment when executing the computer program.
In summary, according to the method and the terminal for identifying and starting the file system by the embedded uboot provided by the invention, when the file system is started by using the uboot minimum system and has a plurality of file systems, automatic identification can be realized for selection, so that smooth starting of the system is ensured, and services on the embedded device can run normally; complicated setting is not needed manually, and a file system can be conveniently started by inexperienced personnel of the uboot; in addition, the invention realizes different operations according to different numbers and types of the mirror image files, and has more pertinence and stronger practicability.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all equivalent changes made by using the contents of the present specification and the drawings, or applied directly or indirectly to the related technical fields, are included in the scope of the present invention.
Claims (10)
1. A method for starting a file system by embedded uboot recognition is characterized by comprising the following steps:
s1, starting the uboot and starting a preset starting menu;
s2, reading the starting mirror image in each partition, setting the starting mirror image as each starting option under the starting menu, and configuring a corresponding starting environment variable for each starting option according to the type of the starting mirror image;
s3, receiving selection information of a user, and starting the file system according to the selected starting option in the selection information and the starting environment variable corresponding to the selected starting option.
2. The method for embedded uboot recognition to start the file system according to claim 1, wherein the step S1 specifically includes:
and starting the uboot, reading the partition number of the storage equipment, judging whether the partition number is greater than 1, and if the partition number is greater than 1, starting a preset starting menu.
3. The method for embedded uboot recognition to boot a file system according to claim 2, wherein the boot image in step S2 includes a ramdisk image and a kernel image.
4. The method for embedded uboot recognition to start the file system according to claim 3, wherein the step S2 specifically comprises:
traversing files in each partition, judging whether the type of the starting mirror image in the partition is the ramdisk mirror image, if so, taking the starting mirror image as one starting option under the starting menu, and setting the name of the ramdisk mirror image as the starting environment variable of the corresponding starting option;
if the current partition is the kernel image mirror image, continuously traversing the files in the current partition, judging whether an init file necessary for starting a file system exists in the current partition, if the init file exists, taking the kernel image mirror image as a starting option under the starting menu, and setting the name of the kernel image mirror image and the partition where the init file is located as the starting environment variable corresponding to the starting option.
5. The method of claim 3, wherein if the number of partitions in step S1 is 1, the method proceeds to step S4:
s4, traversing files in the partition, judging the type of the boot image, if the type of the boot image is the ramdisk image, setting the image name as the boot environment variable, and booting a file system;
otherwise, the type of the starting mirror image is the kernel image mirror image, files in the partition are continuously traversed, whether an init file necessary for starting the file system exists in the current partition is judged, if the init file exists, the name of the kernel image mirror image and the partition where the init file is located are set as the starting environment variable, the file system is started, and otherwise, the starting fails.
6. An embedded uboot recognition starting file system terminal, comprising a processor, a memory and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the computer program to realize the following steps:
s1, starting the uboot and starting a preset starting menu;
s2, reading the starting mirror image in each partition, setting the starting mirror image as each starting option under the starting menu, and configuring a corresponding starting environment variable for each starting option according to the type of the starting mirror image;
s3, receiving selection information of a user, and starting the file system according to the selected starting option in the selection information and the starting environment variable corresponding to the selected starting option.
7. The terminal for embedded uboot recognition based file system startup according to claim 6, wherein the step S1 specifically includes:
and starting the uboot, reading the partition number of the storage equipment, judging whether the partition number is greater than 1, and if the partition number is greater than 1, starting a preset starting menu.
8. The embedded uboot recognition bootable file system terminal of claim 7, wherein the boot image in step S2 includes a ramdisk image and a kernel image.
9. The terminal for embedded uboot recognition based file system startup according to claim 8, wherein the step S2 specifically includes:
traversing files in each partition, judging whether the type of the starting mirror image in the partition is the ramdisk mirror image, if so, taking the starting mirror image as one starting option under the starting menu, and setting the name of the ramdisk mirror image as the starting environment variable of the corresponding starting option;
if the current partition is the kernel image mirror image, continuously traversing the files in the current partition, judging whether an init file necessary for starting a file system exists in the current partition, if the init file exists, taking the kernel image mirror image as a starting option under the starting menu, and setting the name of the kernel image mirror image and the partition where the init file is located as the starting environment variable corresponding to the starting option.
10. The terminal of claim 8, wherein when the processor executes the computer program, if the number of partitions in step S1 is 1, the process proceeds to step S4:
s4, traversing files in the partition, judging the type of the boot image, if the type of the boot image is the ramdisk image, setting the image name as the boot environment variable, and booting a file system;
otherwise, the type of the starting mirror image is the kernel image mirror image, files in the partition are continuously traversed, whether an init file necessary for starting the file system exists in the current partition is judged, if the init file exists, the name of the kernel image mirror image and the partition where the init file is located are set as the starting environment variable, the file system is started, and otherwise, the starting fails.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011451034.4A CN112433772A (en) | 2020-12-10 | 2020-12-10 | Method and terminal for embedded uboot recognition starting of file system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011451034.4A CN112433772A (en) | 2020-12-10 | 2020-12-10 | Method and terminal for embedded uboot recognition starting of file system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112433772A true CN112433772A (en) | 2021-03-02 |
Family
ID=74691109
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011451034.4A Pending CN112433772A (en) | 2020-12-10 | 2020-12-10 | Method and terminal for embedded uboot recognition starting of file system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112433772A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106951257A (en) * | 2017-03-24 | 2017-07-14 | 济南浪潮高新科技投资发展有限公司 | A kind of implementation method for starting WinCE with Uboot_CDROM |
| CN108415733A (en) * | 2018-02-06 | 2018-08-17 | 上海康斐信息技术有限公司 | A kind of startup method and device of the router based on double-mirror Flash |
| US20190273830A1 (en) * | 2018-03-02 | 2019-09-05 | Brother Kogyo Kabushiki Kaisha | Non-Transitory Computer-Readable Recording Medium Containing Instructions Causing Device to Download Data from Server |
-
2020
- 2020-12-10 CN CN202011451034.4A patent/CN112433772A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106951257A (en) * | 2017-03-24 | 2017-07-14 | 济南浪潮高新科技投资发展有限公司 | A kind of implementation method for starting WinCE with Uboot_CDROM |
| CN108415733A (en) * | 2018-02-06 | 2018-08-17 | 上海康斐信息技术有限公司 | A kind of startup method and device of the router based on double-mirror Flash |
| US20190273830A1 (en) * | 2018-03-02 | 2019-09-05 | Brother Kogyo Kabushiki Kaisha | Non-Transitory Computer-Readable Recording Medium Containing Instructions Causing Device to Download Data from Server |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7237238B2 (en) | Method and apparatus for automated operating systems upgrade | |
| US8352721B1 (en) | Initiating an operating system boot from firmware | |
| US9301164B2 (en) | Method, system, and terminal for performing system update between mobile communication terminals | |
| US8751783B2 (en) | Booting computing devices with EFI aware operating systems | |
| US7689802B2 (en) | Controlling memory access in a multi-booting system | |
| US6725178B2 (en) | Use of hidden partitions in a storage device for storing BIOS extension files | |
| US6804774B1 (en) | Software image transition aid comprising building a disk image based on identified hardware | |
| US8291209B2 (en) | Integration model for instant-on environment | |
| US7694125B2 (en) | System and method of booting an operating system in an optimal performance state | |
| US7962736B1 (en) | Interactive pre-OS firmware update with repeated disabling of interrupts | |
| JPH08249191A (en) | Method and equipment for boot | |
| CN110737479A (en) | method for starting operating system without disk, server and readable storage medium | |
| US11704198B2 (en) | Method and apparatus for providing recovery from a computing device boot up error | |
| US9965292B2 (en) | Method of bluetooth pairing with UEFI firmware and computer system thereof | |
| US7484083B1 (en) | Method, apparatus, and computer-readable medium for utilizing BIOS boot specification compliant devices within an extensible firmware interface environment | |
| US20190068772A1 (en) | Computer system and method thereof for bluetooth data sharing between uefi firmware and os | |
| US20050223209A1 (en) | Apparatus for fast booting computer and method for the same | |
| US9727390B1 (en) | Invoking a firmware function | |
| KR20000052312A (en) | Method and apparatus for determining the drive letter assignment of a CD ROM drive during initial system setup of a computer system | |
| CN116009899B (en) | Mirror image making method and device of operating system, electronic equipment and storage medium | |
| CN112433772A (en) | Method and terminal for embedded uboot recognition starting of file system | |
| CN102455919A (en) | Automatic optimization setting method for basic input output system(BIOS) | |
| CN115291951A (en) | UEFI (unified extensible firmware interface) starting method and device, electronic equipment and storage medium | |
| WO2008048581A1 (en) | A processing device operation initialization system | |
| CN113342365A (en) | Operating system deployment method, device, equipment and computer-readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20210302 |