WO2013135047A1

WO2013135047A1 - Method for single-board plug and play, single-board and system therefor

Info

Publication number: WO2013135047A1
Application number: PCT/CN2012/083488
Authority: WO
Inventors: 景玉超; 刘永合
Original assignee: 华为技术有限公司
Priority date: 2012-03-14
Filing date: 2012-10-25
Publication date: 2013-09-19
Also published as: CN102629209A; CN102629209B

Abstract

Disclosed are a method for single-board plug and play, a single-board and a system therefor, belonging to the technical field of computer applications. The method comprises: enabling a BIOS program after the single-board powers on; a new driver file previously stored in the single-board and which needs to be updated is copied by the BIOS program to a system reserved memory; starting bzImage; running Initrd, a program wherein reads the new driver file from the system reserved memory and replaces the old driver file in the Initrd; after loading the driver file, executing start-up of the next program of the single-board operating system. The method utilizes an on-board change component to load new driver files on the single-board, hence before a driver is loaded, the old driver file of the element to be changed is replaced by a new driver file, thus simplifying single-board software up-grades, simplifying operations, and improving work efficiency and maintainability.

Description

Plug-and-play method, board and system for implementing single board

This application claims the priority of the Chinese application filed on March 14, 2012, the application number is 201210066368.9, and the invention is entitled "Implementation of a single-panel plug-and-play method, board and system", the entire contents of which are incorporated by reference. In this application.

Technical field

The present invention relates to the field of computer application technologies, and in particular, to a method, a single board, and a system for implementing plug and play of a single board.

Background of the invention

Due to its open source and stability, Linux systems are widely used in many fields. Whether it is an embedded board with relatively few resources or a large server board with abundant resources, Linux systems run on it. Linux The system has extensive technical support and rich hardware and software resources. In the actual use environment, considering the cost savings, the resources on the board are relatively small, the Linux system software version is simplified as much as possible, and only the drivers and scripts related to the single board hardware are integrated, so that the system can be made normal on a limited resource. run.

Minimize the file size of the released version during the development of the existing Linux system, and use the following methods to handle:

Embedded board: The existing embedded board, the software version mainly releases bzImage and Initrd, and the driver of the board is placed in Initrd. If the peripheral device of the board changes, the driver is incompatible. In this case, bzImage must be re-released. And the Initrd file, the board can be loaded normally.

Server board: The existing server board. The software version mainly releases the driver installation package, including the driver and script. When the image is installed, the driver installation package is executed. The board driver and script are placed in the specified directory of the system. The peripheral device changes cause the driver to be incompatible. In this case, you must re-release the driver installation package and reinstall the OS for the board to work properly.

As shown in the above description, after the peripheral device of the board is changed, in order to solve the problem that the board can be plugged and used, bzImage and Initrd need to be re-released for the embedded board, and the driver board is re-released for the server board. The package can realize the plug-and-play of the single board, but it has the problem of complicated operation and increased cost. Moreover, the embedded board or the server board that uses other operating systems with files as the operating unit also has the problem of plug and play after the peripheral device is changed.

Summary of the invention

The embodiment of the present invention provides a method, a board, and a system for implementing a single-board plug-and-play method, which can solve the problem that the new single-board peripheral device is replaced after the replacement of the original single-board peripheral device. Only when the plug-and-play of the new board can be realized, there is a problem that the operation is complicated and the cost is increased.

A method for the plug-and-play of a single board is used to replace the old board with a new board running the Linux system, including:

Start the BIOS program after the board is powered on;

The BIOS program copies a new driver file that is pre-stored on the board and needs to be updated to the system reserved memory;

bzImage starts;

Running Initrd, the program in Initrd reads the new driver file from the system reserved memory and replaces the old driver file in Initrd;

After the driver file is loaded, the startup of the operating system running the board is executed.

Start the BIOS program after the board is powered on;

bzImage starts;

Running Initrd, the program in Initrd reads a portion of the new driver file from the system reserved memory and replaces the old driver file in Initrd;

Load the driver file to start the hard disk file system;

The program in Initrd reads the rest of the new driver file from the system reserved memory and replaces the old driver file in the hard disk file system;

After the driver files in the hard disk file system are loaded, the subsequent programs of the operating system running on the board are started.

A plug-and-play board that replaces the old boards running Linux, including:

CPU, memory, and non-volatile memory; among them,

The non-volatile memory is used to store a BIOS program, a new driver file that needs to be updated, a bzImage program, and an Initrd program;

The memory is used to store data required for the program to run;

The CPU is configured to execute a program;

After the board is powered on, the CPU executes a BIOS program stored in the non-volatile memory, and loads a new driver file pre-stored in the non-volatile memory into the system by executing a BIOS program. In memory

The CPU executes the bzImage program;

The CPU executes the Initrd program, reads the new driver file from the memory and replaces the old driver file in the Initrd;

After the CPU loads the driver file, it starts the startup of the operating system running on the board.

A plug-and-play board that is used to replace an old board running a Linux system, and includes:

CPU, memory, and non-volatile memory; among them,

The memory is used to store data required for the program to run;

The CPU is configured to execute a program;

The CPU executes the bzImage program;

The CPU executes the Initrd program, reads a part of the new driver file from the memory reserved by the system, and replaces the old driver file in the Initrd;

The CPU executes the load driver file to start the hard disk file system;

The CPU executes the Initrd program to read the remaining portion of the new driver file from the memory reserved by the system and replace the old driver file in the hard disk file system;

After the CPU executes the driver file in the hard disk file system, the CPU runs the subsequent programs of the operating system running on the board.

A system for implementing plug and play of a single board, comprising:

The chassis and the plurality of boards are inserted into the chassis, and at least one of the plurality of boards is configured by using the single board.

It can be seen from the technical solution provided by the foregoing that the method provided by the embodiment of the present invention replaces the old driver file with a new driver file of the device before the driver is loaded by using a new driver file on the board to change the device. After the new board is replaced with the old board, it is plug-and-play, which simplifies the software upgrade mode of the board. The operation is simple, and the work efficiency and maintainability are improved.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention, Those of ordinary skill in the art will be able to obtain other figures from these drawings without the inventive effort.

1 is a flowchart of a method for implementing plug and play of a single board according to Embodiment 1 of the present invention;

2 is a flowchart of starting an embedded board according to Embodiment 1 of the present invention;

FIG. 3 is a flowchart of a method for implementing plug-and-play of an embedded single board according to Embodiment 1 of the present invention;

4 is a flowchart of a method for implementing plug-and-play of a single board according to Embodiment 2 of the present invention;

FIG. 5 is a flowchart of a server board startup according to Embodiment 2 of the present invention;

FIG. 6 is a flowchart of a method for implementing plug-and-play of a server board according to Embodiment 2 of the present invention;

FIG. 7 is a schematic structural diagram of a plug-and-play single board according to Embodiment 3 of the present invention;

FIG. 8 is a schematic structural diagram of a plug-and-play single board according to Embodiment 4 of the present invention; FIG.

FIG. 9 is a schematic diagram of a system for implementing plug and play of a single board according to Embodiment 5 of the present invention.

Mode for carrying out the invention

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

The embodiment of the invention provides a method for the plug-and-play of a single board, which can be used to replace the old board with a new board running the Linux system, and can be applied to replace the old embedded board with a new embedded board, such as As shown in Figure 1, the method includes:

Step 1. Start the BIOS program after the board is powered on.

Step 2: The BIOS program copies the new driver file that is pre-stored on the board and needs to be updated to the system reserved memory.

Step 3, bzImage starts;

Step 4: Run Initrd, the program in Initrd reads the new driver file from the system reserved memory and replaces the old driver file in Initrd;

Step 5: After loading the driver file, execute the startup of the operating system running the board (such as starting Dopra).

In the above method, the new driver file that needs to be updated in advance on the board is a plurality of new driver files, and the plurality of new driver files are compressed into a new driver file and the compression package is stored on the board.

In the above method, when the new driver file is a new driver file compression package including a plurality of new driver files, the program in the Initrd reads the new driver file from the system reserved memory and replaces the old driver file in the Initrd including: the program in the Initrd The new driver file compression package read from the system reserved memory is decompressed, and the corresponding new driver files in Initrd are replaced by a plurality of new driver files obtained after decompression.

The above method is applicable to the implementation of plug-and-play after the new embedded board running the Linux operating system replaces the old embedded board.

The following describes the above method in combination with the plug-and-play implementation process of the embedded board and the server board running the Linux system.

First, the embedded board running Linux system is taken as an example:

The current boot process of the embedded board running Linux system is shown in Figure 2. The driver associated with the embedded board is mainly placed in the initrd file (Linux). In the root file system, when the embedded board starts, the BIOS (Operations and Maintenance Unit) must be from OMU (Operations). And Maintenance Unit, operation and maintenance unit) load bzImage (Linux kernel image file) and initrd (Linux kernel image file), bzImage starts after loading successfully, then initrd starts, inserts the board driver during initrd startup process, and finally dopra (Distributed Object-oriented Programable Realtime Architecture, The distributed object-oriented programmable real-time architecture is the next generation of telecom support platform).

The disadvantages of the above-mentioned embedded board startup process are as follows: the embedded board-related driver is placed in the initrd, and the initrd also has the related files of the dopra; if the peripheral components of the embedded board change, then the initrd The driver in the drive also needs to be changed to support the new board. If the initrd file compatible with the new and old boards is released, the initrd file will become larger, and the complexity of the software will increase. increase cost. If the initrd file compatible with the new and old boards is not released, there is no plug and play for the new board.

The processing flow of the method for implementing the plug-and-play method of the embedded board by using the method of the embodiment of the present invention is as shown in FIG. 3 , and specifically includes the following steps:

Step 30: Insert the embedded board running the Linux system (the board is used as a new board to replace the old board);

Step 31: The BIOS of the embedded board is started.

Step 32: The BIOS of the embedded board requests the OMU to load bzImage and initrd (when the bzImage on the OMU supports the current CPU, when the peripheral device of the board changes, the bzImage and the initrd on the OMU do not need to be changed, only need to be loaded. The old bzImage and initrd can be);

Step 33, loading back;

Step 34: The BIOS of the embedded board copies a new driver file (which can be a driver file or multiple driver files, and multiple drive files can be stored in a compressed package) to the system reserved memory.

Step 35, bzImage starts, Linux initializes the system;

In step 36, Initrd starts running and prepares the initrd environment.

Step 37: Before the initrd driver is loaded, the new driver file is read from the system reservation;

Step 38, replacing the old driver file in the initrd with the read new driver file (if the new driver file is multiple and is a compressed package, after decompressing, the obtained new driver files are respectively replaced with the corresponding old ones in the initrd Drive file);

Step 39: Insert the replaced driver file into the board driver in the initrd in the original manner;

In step 310, the Dopra is started, and the insertion of the embedded board driver is completed, and the board can be started normally.

As shown in the above process, the new driver file that changes the device between the new board and the old board is loaded on the new board, and the changed new driver file is copied to the system when the BIOS starts. In the reserved memory, the new driver file is read from the system reserved memory and the old driver file in the initrd is replaced before the related driver is loaded, so that the new card replaces the plug-and-play function of the old board, and the new single is blocked. The difference between the board and the upper layer improves the maintainability of the system. Moreover, the method simplifies the software upgrade mode of the board. If the underlying software has a bug, it only needs to upgrade the driver file of the onboard change device, and does not need to upgrade the entire driver file to improve work efficiency.

Embodiment 2

This embodiment provides a method for the plug-and-play of a single board. The new board is used to replace the old board. The new server board can be used to replace the old server board. Show, including:

Step 40: After the board is powered on, the BIOS program is started.

Step 41: The BIOS program copies the new driver file that is pre-stored on the board and needs to be updated to the system reserved memory.

Step 42, bzImage is started;

Step 43, running Initrd, the program in Initrd reads a part of the new driver file from the system reserved memory and replaces the old driver file in the Initrd;

Step 44: Load the driver file to start the hard disk file system;

Step 45: The program in Initrd reads the remaining part of the new driver file from the system reserved memory and replaces the old driver file in the hard disk file system;

Step 46: After loading the driver file in the hard disk file system, perform the startup of the operating system running the board (such as starting Dopra).

In the above method, the new driver file that needs to be updated in advance on the board may be a plurality of new driver files, and the plurality of new driver files are compressed into a new driver file and the compression package is stored on the board.

In the above method, if the new driver file is a new driver file compression package including a plurality of new driver files, the program in the Initrd reads a part of the new driver file from the system reserved memory and replaces the old driver file in the Initrd as: The program in Initrd decompresses the new driver file compression package read from the system reserved memory, and replaces the corresponding old driver file in Initrd with the new driver file corresponding to the hard disk device among the plurality of new driver files obtained after decompression. .

In the above method, the program in Initrd reads the rest of the new driver file from the system reserved memory and replaces the old driver file in the hard disk file system including:

The program in Initrd replaces the new drive file in the hard disk file system with the new drive file of the remaining part of the new drive file obtained by decompressing the new drive file compression package read from the system reserved memory.

The above method is applicable to the implementation of plug and play after the new server board running the Linux operating system replaces the old server board.

The following takes the server board running Linux as an example:

The current startup process of the server board running Linux system is shown in Figure 5. The startup of the server board is more complicated than that of the embedded board. The main reason is that it must be run in the ram root file system, first load a part of the driver, especially It is necessary to load the hard disk drive, mount the hard disk partition after finding the hard disk, and then switch the root file system from the ram (memory) to the hard disk partition; after the hard disk root file system is started, continue to load the single board driver, and finally start dopra.

The shortcomings of the above startup process are: if the peripheral components of the server board change, if the driver software changes, the server system will face the same problem of the embedded system, and more serious if the hard disk controller changes, the system It will not start properly, unless the system is reinstalled, the plug-and-play of the server board can be realized.

The processing flow of the method for implementing the plug-and-play method of the server board running the Linux system by using the method of the embodiment of the present invention is as shown in FIG. 6 , and specifically includes the following steps:

Step 50: After the server running the Linux system is powered on, the board is used as a new board to replace the old board.

Step 51: The BIOS of the server board is started.

Step 52: The BIOS of the server board copies the new driver file on the board that is matched with the board to the system reserved memory.

Step 53: The server board runs the GRUB boot of the Linux system, and loads the bzImage and the initrd from the hard disk boot partition to the memory;

Step 54, bzImage is started, and the system is initialized;

Step 55, initrd starts, ready for the initrd environment;

Step 56: Read the new driver file from the system reserved memory before the initrd driver loads;

Step 57, replacing the corresponding old driver file in the initrd with a part of the driver file in the new driver file, that is, replacing the old driver file corresponding to the hard disk setting in the initrd with the driver file corresponding to the hard disk device in the new driver file;

Step 58: After the replacement is completed, insert the driver file into the driver of the initrd according to the original manner, and find the hard disk device;

Step 59: Mount the hard disk partition and switch the root file system.

Step 510, the hard disk file system is started;

Step 511, replacing the old driver file in the hard disk file system with the remaining driver files in the new driver file, that is, replacing the old driver file in the corresponding part of the hard disk file system with the remaining driver files in the new driver file;

Step 512, insert the replaced driver file into the driver of the hard disk file system;

In step 513, the dopra is started, and the driver insertion of the server board is completed, and the subsequent startup of the server board can be implemented.

It can be seen from the foregoing process that the method of the embodiment of the present invention uses a new driver file that is changed on the new board and the new driver file of the new board is changed on the new board. When the BIOS starts, the new driver file is copied to the system reserved memory. Before the relevant driver is loaded, the new driver file is read from the system reserved memory, and the corresponding old driver file in the initrd is replaced, so that the new board replaces the old ticket. The plug-and-play function behind the board shields the difference between the board and the upper layer and improves the maintainability of the system. Moreover, the method simplifies the software upgrade of the board. If there is a bug in the underlying software, only the driver file of the onboard change needs to be upgraded, and the entire driver file package does not need to be upgraded, thereby improving work efficiency.

Embodiment 3

This embodiment provides a plug-and-play board, which is used to replace an old board running Linux. It can be used as an embedded board. As shown in Figure 7, the board includes: CPU, memory, and Non-volatile memory; each component can be soldered to a printed circuit of a single board and electrically connected through a printed circuit;

Wherein, the non-volatile memory is used for storing a BIOS program, a new driver file that needs to be updated, a bzImage program, and an Initrd program;

Memory is used to store the data needed to run the program;

The CPU is used to execute the program;

The CPU executes the bzImage program;

In the above-mentioned board, when the CPU executes the Initrd program to read the new driver file from the memory reserved by the system into a compressed package containing a plurality of new driver files, the CPU executes the Initrd program to read the new memory from the system reserved. The driver file compression package is decompressed, and the corresponding new driver files in Initrd are replaced by a plurality of new driver files obtained after decompression.

Embodiment 4

The embodiment provides a plug-and-play board, which is used to replace the old board running the Linux system, and can be used as a server board, as shown in FIG. 8, the CPU, the memory, and the non-volatile memory; The components can be soldered to the printed circuit of the board and electrically connected through the printed circuit;

Memory is used to store the data needed to run the program;

The CPU is used to execute the program;

The CPU executes the bzImage program;

The CPU executes the load driver file to start the hard disk file system;

Among the above boards, When the CPU executes the Initrd program to read a new driver file from the memory reserved in the system to a compressed package containing a plurality of new driver files, the CPU executes a new driver file compression package that the Initrd program reads from the system reserved memory. Decompressing, replacing the corresponding old driver file in Initrd with the new driver file corresponding to the hard disk device among the plurality of new driver files obtained after decompressing.

In the above-mentioned board, the CPU executes the program in Initrd to read the remaining part of the new driver file from the memory reserved by the system and replace the old driver file in the hard disk file system, including:

The CPU executes the program in Initrd to replace the new driver file of the remaining part of the new driver file obtained by decompressing the new driver file compressed in the memory reserved by the system, respectively, with the corresponding old driver file in the hard disk file system.

Embodiment 5

This embodiment provides a system for implementing plug and play of a single board. As shown in FIG. 9, the system includes:

The chassis 80 and the plurality of boards 81 to 8n are inserted into the chassis 80. At least one of the plurality of boards 81 to 8n is provided by the third or fourth embodiment. veneer.

In the method of the embodiment of the present invention, the new driver file is changed on the board, and the driver file of the new board is changed on the new board, and the newly changed driver file is copied to the BIOS when the BIOS is started. The system is reserved in the memory. Before the related driver is loaded, the driver file is read from the system reserved memory, and the driver file in the Initrd program is replaced, so that the plug-and-play function of the old board is replaced by the new board, and the board is shielded. Improve the maintainability of the system by making differences to the upper layers. Moreover, the method simplifies the software upgrade of the board. If there is a bug in the underlying software, only the onboard change driver file needs to be upgraded, and the entire driver file does not need to be upgraded, thereby improving work efficiency.

It should be noted that if there are other operating systems similar to the operating system similar to the Linux operating system, for example, the operating system can also replace the old driver files with new driver files during startup or operating system execution, and can also modify some The code of the program (similar to the Initrd program) is used to complete the replacement action, then it should be considered that these solutions adopt basically similar technical means to achieve the same technical problems, and achieve substantially the same technical effect, which is a kind of this embodiment. Equivalent alternatives are also intended to be covered by the scope of the invention.

The above is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or within the technical scope of the present disclosure. Alternatives are intended to be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Claims

A method for implementing a single-board plug-and-play method, which is applied to a new board running a Linux system to replace the old board, and includes:

Start the BIOS program after the board is powered on;

The BIOS program copies a new driver file that is pre-stored on the board and needs to be updated to the system reserved memory;

bzImage starts;

Running Initrd, the program in Initrd reads the new driver file from the system reserved memory and replaces the old driver file in Initrd;

After the driver file is loaded, the startup of the operating system running the board is executed.
The method according to claim 1, wherein the new drive file that is pre-stored on the board and needs to be updated is a plurality of new drive files, and the plurality of new drive files are compressed into a new drive file compression package storage. On the board.
The method according to claim 1, wherein the program in the Initrd reads a new driver file from the system reserved memory and replaces the old driver file in the Initrd, including:

If the new driver file is a new driver file package including multiple new driver files, the program in Initrd decompresses the new driver file compression package read from the system reserved memory, and decompresses multiple new drivers. The files replace the corresponding old driver files in Initrd.
A method for implementing a single-board plug-and-play method, which is applied to a new board running a Linux system to replace the old board, and includes:

Start the BIOS program after the board is powered on;

The BIOS program copies a new driver file that is pre-stored on the board and needs to be updated to the system reserved memory;

bzImage starts;

Running Initrd, the program in Initrd reads a portion of the new driver file from the system reserved memory and replaces the old driver file in Initrd;

Load the driver file to start the hard disk file system;

The program in Initrd reads the rest of the new driver file from the system reserved memory and replaces the old driver file in the hard disk file system;

After the driver files in the hard disk file system are loaded, the subsequent programs of the operating system running on the board are started.
The method according to claim 4, wherein the new drive file that is pre-stored on the board and needs to be updated is a plurality of new drive files, and the plurality of new drive files are compressed into a new drive file. On the board.
The method according to claim 4, wherein the program in the Initrd reads a part of the new driver file from the system reserved memory and replaces the old driver file in the Initrd includes:

If the new driver file is a new driver file package including multiple new driver files, the program in Initrd decompresses the new driver file compression package read from the system reserved memory, and decompresses multiple new drivers. The new driver file corresponding to the hard disk device in the file replaces the corresponding old driver file in Initrd.
The method according to claim 6, wherein the program in the Initrd reads the remaining portion of the new driver file from the system reserved memory and replaces the old driver file in the hard disk file system, including:

The program in Initrd replaces the new drive file in the hard disk file system with the new drive file of the remaining part of the new drive file obtained by decompressing the new drive file compression package read from the system reserved memory.
A plug-and-play board that is used to replace an old board running a Linux system, and includes:

CPU, memory, and non-volatile memory; among them,

The non-volatile memory is used to store a BIOS program, a new driver file that needs to be updated, a bzImage program, and an Initrd program;

The memory is used to store data required for the program to run;

The CPU is configured to execute a program;

After the board is powered on, the CPU executes a BIOS program stored in the non-volatile memory, and loads a new driver file pre-stored in the non-volatile memory into the system by executing a BIOS program. In memory

The CPU executes the bzImage program;

The CPU executes the Initrd program, reads the new driver file from the memory and replaces the old driver file in the Initrd;

After the CPU loads the driver file, it starts the startup of the operating system running on the board.
The board according to claim 8, wherein the CPU executes the Initrd program when the CPU executes the Initrd program to read the new driver file from the memory reserved by the system into a compressed package containing a plurality of new driver files. The new driver file compression package read from the memory reserved by the system is decompressed, and the corresponding new driver files in Initrd are replaced by a plurality of new driver files obtained after decompression.
A plug-and-play board that is used to replace an old board running a Linux system, and includes:

CPU, memory, and non-volatile memory; among them,

The non-volatile memory is used to store a BIOS program, a new driver file that needs to be updated, a bzImage program, and an Initrd program;

The memory is used to store data required for the program to run;

The CPU is configured to execute a program;

After the board is powered on, the CPU executes a BIOS program stored in the non-volatile memory, and loads a new driver file pre-stored in the non-volatile memory into the system by executing a BIOS program. In memory

The CPU executes the bzImage program;

The CPU executes the Initrd program, reads a part of the new driver file from the memory reserved by the system, and replaces the old driver file in the Initrd;

The CPU executes the load driver file to start the hard disk file system;

The CPU executes the Initrd program to read the remaining portion of the new driver file from the memory reserved by the system and replace the old driver file in the hard disk file system;

After the CPU executes the driver file in the hard disk file system, the CPU runs the subsequent programs of the operating system running on the board.
The board according to claim 10, wherein when the CPU executes the Initrd program to read the new driver file into the memory in the memory reserved by the system as a compressed package including a plurality of new driver files, the CPU executes The Initrd program decompresses the new driver file compression package read from the memory reserved by the system, and replaces the corresponding old driver file in the Initrd with the new driver file corresponding to the hard disk device among the plurality of new driver files obtained after decompression.
The method according to claim 11, wherein the CPU executes a program in the Initrd to read the remaining portion of the new driver file from the memory reserved by the system and replace the old driver file in the hard disk file system, including:

The CPU executes the program in Initrd to replace the new driver file of the remaining part of the new driver file obtained by decompressing the new driver file compressed in the memory reserved by the system, respectively, with the corresponding old driver file in the hard disk file system.
A system for implementing plug and play of a single board, comprising:

The chassis and the plurality of boards are inserted into the chassis, wherein at least one of the plurality of boards is used according to any one of claims 8 to 9 or any one of claims 10 to 12. The board described.