CN105278993A - Linux system based drive module upgrading method and apparatus - Google Patents
Linux system based drive module upgrading method and apparatus Download PDFInfo
- Publication number
- CN105278993A CN105278993A CN201510708566.4A CN201510708566A CN105278993A CN 105278993 A CN105278993 A CN 105278993A CN 201510708566 A CN201510708566 A CN 201510708566A CN 105278993 A CN105278993 A CN 105278993A
- Authority
- CN
- China
- Prior art keywords
- module
- target drives
- depending
- version
- drives module
- 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.)
- Granted
Links
Landscapes
- Stored Programmes (AREA)
Abstract
The present invention discloses a Linux system based drive module upgrading method. The method comprises: receiving a drive module upgrading instruction, and determining an original version and an upgraded version of a target drive module corresponding to the drive module upgrading instruction; acquiring a depending module of the target drive module and a dependency relationship between the target drive module and the depending module; unloading the original version of the target drive module and the depending module according to the dependency relationship; and loading the upgraded version of the target drive module and the depending module according to the dependency relationship. The present invention further provides a Linux system based drive module upgrading apparatus. With adoption of the Linux system based driving module upgrading method and apparatus provided by the present invention, a drive module upgrading problem in the Linux system is optimized, so that stability and reliability of the system can be improved.
Description
Technical field
The present invention relates to electronic technology field, particularly relate to a kind of driver module upgrade method based on linux system and device.
Background technology
Based on the Set Top Box of (SuSE) Linux OS, when upgrading driver module, the driver module first unloading legacy version is needed to be loaded into the driver module of redaction again, if the driver module of legacy version also depends on other modules, so also need to unload the module with the driver module of legacy version with dependence.When loading redaction, also need the driver module according to the sequential loading redaction of dependence and Depending module thereof.In prior art, Linux order provides a kind of modprobe order, can modprobe, i.e. the automatic decision sequencing that will insmod be loaded into corresponding module in order.
But, the versatility of modprobe order is not enough, in the Linux system of a lot of cutting, all cannot use modprobe order, cause upgrade driver module time, driver module just cannot according to correct order unloaded and loading, may cause needing to restart Set Top Box with initialization driver module, even cause driver module to run, thus cause the instability of system cloud gray model, the reliability of influential system.On the other hand, modprobe order needs to preserve file regularly, namely needs certain space and dependence, if rely on destroyed or produce the unsuccessful correctness that can affect driver module.
Summary of the invention
Embodiment of the present invention technical matters to be solved is, provides a kind of driver module upgrade method based on linux system and device, to optimizing the driver module upgrade problem in Linux system, and then the stability of elevator system and reliability.
Embodiments provide a kind of driver module upgrade method based on linux system, the method comprises:
Receive driver module upgrade, determine prototype version and the upgraded version of the target drives module that described driver module upgrade is corresponding;
The Depending module obtaining described target drives module and the dependence existed between described target drives module and described Depending module;
According to described dependence, unload the prototype version of described target drives module and described Depending module;
According to described dependence, be loaded into the upgraded version of described target drives module and described Depending module.
Correspondingly, the embodiment of the present invention additionally provides a kind of driver module update device based on linux system, and this device comprises:
Target determination module, for receiving driver module upgrade, determines prototype version and the upgraded version of the target drives module that described driver module upgrade is corresponding;
Rely on acquisition module, for the Depending module that obtains described target drives module and the dependence existed between described target drives module and described Depending module;
Unload module, for according to described dependence, unloads the prototype version of described target drives module and described Depending module;
Upgraded module, for according to described dependence, is loaded into the upgraded version of described target drives module and described Depending module.
The embodiment of the present invention is according to the Depending module of the target drives module got and the dependence that exists between target drives module and Depending module, the prototype version of unloading target drives module and Depending module, and be loaded into upgraded version and the Depending module of target drives module, the driver module upgrade problem in Linux system can be optimized, and then the stability of elevator system and reliability.
Accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.
Fig. 1 is the schematic flow sheet of a kind of driver module upgrade method based on linux system in the embodiment of the present invention;
Fig. 2 is the composition structural drawing of a kind of driver module update device based on linux system in the embodiment of the present invention;
Fig. 3 is the schematic diagram of the dependency tiee of a kind of driver module and Depending module in the embodiment of the present invention;
Fig. 4 is the schematic diagram of the dependency tiee of a kind of driver module and Depending module in the embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, be clearly and completely described the technical scheme in the embodiment of the present invention, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
In order to optimize the driver upgrade problem of Linux system, the embodiment of the present invention proposes a kind of driver module upgrade method based on linux system, the computer program that this method flow process can depend on based on linux system is implemented, this computer program can run on the computer system of von Neumann system, and this computer system can for having the Set Top Box, intelligent television etc. of linux system.Fig. 1 is the schematic flow sheet of a kind of driver module upgrade method based on linux system in the embodiment of the present invention, and described method at least comprises as shown in the figure:
Step S101, receives driver module upgrade, determines prototype version and the upgraded version of the target drives module that described driver module upgrade is corresponding.
Concrete, target drives module is the driver module that user selectes, the prototype version of target drives module here and upgraded version, and its essence is also all target drives module.The prototype version of target drives module can refer to the version of also not upgrading that target drives module is using, the upgraded version of target drives module can be the version upgraded compared with prototype version that is that user specifies, Set Top Box detects or that receive from other-end, alternatively, be to the improvement of the leak in prototype version and defect and the version after optimizing.
In the present embodiment, user can select target driver module, then prototype version and the upgraded version of this target drives module is selected, click is determined to trigger driver module upgrade, after then Set Top Box receives this driver module upgrade, prototype version and the upgraded version of target drives module and this target drives mould can be determined.In another embodiment, Set Top Box also can trigger after for the driver module upgrade of target drives module user, and intelligent detection also obtains prototype version corresponding to target drives module and upgraded version.
It should be noted that, when Set Top Box obtains prototype version corresponding to target drives module and upgraded version, if upgraded version has been stored in Set Top Box, then Set Top Box has directly obtained upgraded version; If upgraded version is not present in Set Top Box, then Set Top Box can to the upgraded version of receiving target driver module after other-end or server request.
Step S102, the Depending module obtaining described target drives module and the dependence existed between described target drives module and described Depending module.
Concrete, dependence can refer to startup needs of a certain service with another existence of serving and startup for condition.Such as, A service depends on B service, and when needs start A service time, B service must exist and be starting state, otherwise A service cannot start.Relation as A and B just can be called dependence, and namely A service depends on B service.
In the present embodiment, the Depending module of target drives module can refer to the module with target drives module with dependence, and dependence then feeling the pulse with the finger-tip mark driver module depends on this kind of relation that its Depending module just can start or run.Set Top Box after determining target drives module, the Depending module that can obtain target drives module and the dependence existed between target drives module and Depending module.
In concrete enforcement, target drives module can not have Depending module, can have multiple Depending module yet.When target drives module has multiple Depending module, in fact the dependence between the target drives module that Set Top Box obtains and its Depending module is the equal of the dependency tiee of target drives module and its Depending module.Dependency tiee as shown in Figure 3, if A is target drives module, A and B, C, D are connected respectively and mean that A depends on B Depending module, C Depending module and D Depending module respectively.
Further, the Depending module of target drives module also can have the module of Existence dependency relationship with it, then according to the dependence between each module, can obtain more complete dependency tiee.Dependency tiee as shown in Figure 4, can find out that being easy to the dependence obtained between A ~ G is: A depends on B, C, D, and B depends on E, F, and F depends on G again.
Step S103, according to described dependence, unloads the prototype version of described target drives module and described Depending module.
Concrete, in order to be loaded into the upgraded version of target drives module, Set Top Box first will unload the prototype version of target drives module, and when target drives module Existence dependency module, then just can complete the upgraded version of target drives module and the loading of Depending module after also the Depending module of target drives module also will being unloaded.
In concrete enforcement, after getting the dependence existed between target drives module and Depending module in step s 102, Set Top Box just according to dependence, can have the prototype version and Depending module that sequentially unload target drives module.That is, target drives module depends on Depending module, after Set Top Box then can first unload the prototype version of target drives module, then unloads Depending module.
When there is multiple Depending module in target drives module, if the dependence between Depending module with target drives module is parallel, namely be all the Depending module with first nodes in the dependency tiee being in target drives module, and Depending module mutually between also there is no dependence, then Set Top Box can unload all Depending modules according to random order.
Such as, dependency tiee as shown in Figure 3, B, C, D are in the same first nodes of dependency tiee, after then Set Top Box has unloaded A, can unload from B, then unload C and D successively, also can unload successively with the order of C, D, B, can also unload etc. successively with the order of D, C, B.
Further, when the Depending module of target drives module also has the module of Existence dependency relationship with it, Set Top Box can according to the dependency tiee got, according to the order that node highest in dependency tiee unloads to lowermost level node, unload prototype version and the Depending module of target drives module successively.
Such as, dependency tiee as shown in Figure 4, A is in highest node in dependency tiee, and G is in lowermost level node in dependency tiee, then Set Top Box can unload from A, then unloads B, C, D, then unloads E and F, finally unload G.
Step S104, according to described dependence, is loaded into the upgraded version of described target drives module and described Depending module.
Concrete, could running or start because target drives module depends on Depending module, therefore, when being loaded into the upgraded version of target drives module, also the Depending module of target drives module will be loaded into together.
In concrete enforcement, loading order according to getting the dependence existed between target drives module and Depending module in step S102, can have the prototype version and Depending module that are sequentially loaded into target drives module.That is, target drives module depends on Depending module, after Set Top Box then first can be loaded into Depending module, then is loaded into the upgraded version of target drives module.
When there is multiple Depending module in target drives module, if the dependence between Depending module with target drives module is parallel, namely be all the Depending module with first nodes in the dependency tiee being in target drives module, and Depending module mutually between also there is no dependence, then Set Top Box can be loaded into all Depending modules according to random order, is finally loaded into the upgraded version of target drives module.
Such as, dependency tiee as shown in Figure 3, B, C, D are in the same first nodes of dependency tiee, then Set Top Box can be loaded into from B, then be loaded into C and D successively, also can be loaded into successively with the order of C, D, B, can also be loaded into successively with the order of D, C, B, after B, C, D being all loaded into, then be loaded into A.
Further, when the Depending module of target drives module also has the module of Existence dependency relationship with it, Set Top Box can according to the dependency tiee got, the order be loaded into highest node according to lowermost level node in dependency tiee, is finally loaded into the upgraded version of target drives module.
Such as, dependency tiee as shown in Figure 4, G is in lowermost level node in dependency tiee, then Set Top Box can be loaded into from G, is then loaded into E and F, then is loaded into B, C, D, be finally loaded into A.
In an alternative embodiment, when detecting that the upgraded version of described target drives module is loaded into mistake, the prototype version of described target drives module and described Depending module is again loaded into according to described dependence.
Concrete, when step S104 occurs being loaded into mistake, target drives module just cannot normally be run.Now, Set Top Box can be loaded into prototype version and the Depending module of target drives module again according to described dependence.It should be noted that, the prototype version of target drives module can be Set Top Box unloading but not store when its file erase here, also can be the backup file that Set Top Box prestores, not do concrete restriction here.
In concrete enforcement, loading method in its loading method and step S104 is basically identical, namely according to the dependence obtained in step S102, according to the order being loaded into target drives module after being first loaded into Depending module, prototype version and the Depending module of target drives module is again loaded into successively.
In another embodiment, step S101 also comprises: the upgrade file receiving described target drives module corresponding to described driver module upgrade, check information is comprised in described upgrade file, the check information of described upgrade file is verified, if verification is passed through, then using the upgraded version of described upgrade file as described target drives module.
Concrete, after the instruction of user's input queued switches module upgrade, Set Top Box can have the server of annexation or other-end device request to obtain the upgrade file of target drives module to Set Top Box.The upgrade file of target drives module can be set to binary file, wherein can carry the check informations such as cyclic redundancy check (CRC) code (CRC), digital signature, kernel version, equipment Serial Number and software version number.After Set Top Box receives the upgrade file of target drives module, the comparison approval of CRC check and digital signature, kernel version, equipment Serial Number and software version number can be carried out to upgrade file, if verification is passed through, then illustrate that upgrade file is errorless, namely the upgrade file that the upgrade file that receives of Set Top Box and server or other-end equipment send is consistent, then upgrade file can be defined as the upgraded version of target drives module by Set Top Box.
Such as, server or the other-end equipment of annexation is had with Set Top Box, according to the k position binary message code of the upgrade file that will transmit, produce a r position CRC code be attached to binary message code back, k position with the rule preset, form a new upgrade file with the binary message code of common k+r position and send to Set Top Box.After Set Top Box receives upgrade file, can test according to the preset rules followed between binary message code and CRC code, to determine whether make mistakes in transmission.
Again such as, the digital signature received, kernel version, equipment Serial Number and software version number are compared with corresponding digital signature, kernel version, equipment Serial Number and the software version number be pre-stored in Set Top Box by Set Top Box, if after comparison, corresponding check information is all consistent, then determine that transmission is errorless, otherwise, illustrate that this upgrade file does not meet the upgrade file verification attribute of this Set Top Box requirement.
In another embodiment, step S101 also comprises: whether the prototype version detecting described target drives module exists, and if not, is loaded into the upgraded version of described target drives module; If so, step S102 is performed.
Concrete, before Set Top Box gets prototype version corresponding to target drives module, whether the prototype version that first can detect target drives module exists.
If find after detecting, the prototype version of target drives module does not exist, then can directly by the upgraded version load machine top box of target drives module, and the step be loaded into again after not needing to unload the prototype version of target drives module again.Further, if in the upgraded version of target drives module with the Depending module of target drives module Existence dependency relationship, can first Depending module be loaded into, then by the upgraded version load machine top box of target drives module.
If detect, the prototype version of target drives module exists, then perform step S102.
In another embodiment, step S102 also comprises: whether the Depending module detecting described target drives module exists, if not, unload the prototype version of described target drives module, be loaded into the upgraded version of described target drives module, if so, perform step S103.
Concrete, before the Depending module obtaining target drives module in Set Top Box and the dependence existed between target drives module and Depending module, whether the Depending module that first can detect target drives module exists.
If find after detecting, the Depending module of target drives module does not exist, also be target drives module and other modules need not be relied on to carry out starting or running, then directly can unload the prototype version of target drives module, be loaded into the upgraded version of target drives module, and do not need remove to unload the prototype version of target drives module according to the dependence of target drives module and Depending module or be loaded into the upgraded version of target drives module again.
If detect, the Depending module of target drives module exists, then perform step S103.
The embodiment of the present invention is according to the Depending module of the target drives module got and the dependence that exists between target drives module and Depending module, there are the prototype version and Depending module that sequentially unload target drives module, and according to dependence, there are the upgraded version and Depending module that are sequentially loaded into target drives module, thus complete the upgrading of target drives module, the driver module upgrade problem in Linux system can be optimized, and then the stability of elevator system and reliability.Further, present invention also adds the CRC check after receiving upgrade file, digital signature, the contrast of kernel version, equipment Serial Number contrast and software version number inspection, the verification scheme of simple version verification is only done when optimizing modprobe order upgrading driver module, in addition, also add reduction mechanism when upgrading occurs wrong, thus improve stability and the reliability of system further.
In order to optimize the driver upgrade problem of Linux system, the embodiment of the present invention correspondingly proposes a kind of driver module update device based on linux system, this device comprises: target determination module 210, dependence acquisition module 220, Unload module 230 and upgraded module 240, wherein:
Target determination module 210, for receiving driver module upgrade, determines prototype version and the upgraded version of the target drives module that described driver module upgrade is corresponding.
In one embodiment, target determination module 210 also for: whether the prototype version detecting described target drives module exists, and if not, is loaded into the upgraded version of described target drives module, if so, calls described dependence acquisition module 220.
In one embodiment, target determination module 210 is also for the upgrade file that receives described target drives module corresponding to described driver module upgrade, check information is comprised in described upgrade file, the check information of described upgrade file is verified, if verification is passed through, then using the upgraded version of described upgrade file as described target drives module.
Rely on acquisition module 220, for the Depending module that obtains described target drives module and the dependence existed between described target drives module and described Depending module.
In one embodiment, rely on acquisition module 220 also for: whether the Depending module detecting described target drives module exists, if not, unload the prototype version of described target drives module, be loaded into the upgraded version of described target drives module, if so, call described Unload module 230.
Unload module 230, for according to described dependence, unloads the prototype version of described target drives module and described Depending module.
Upgraded module 240, for according to described dependence, is loaded into the upgraded version of described target drives module and described Depending module.
Optionally, this device also comprises: recovery module 250, for when detecting that the upgraded version of described driver module is loaded into mistake, is again loaded into the prototype version of described target drives module and described Depending module according to described dependence.
The embodiment of the present invention is according to the Depending module of the target drives module got and the dependence that exists between target drives module and Depending module, there are the prototype version and Depending module that sequentially unload target drives module, and according to dependence, there are the upgraded version and Depending module that are sequentially loaded into target drives module, thus complete the upgrading of target drives module, the driver module upgrade problem in Linux system can be optimized, and then the stability of elevator system and reliability.Further, present invention also adds the CRC check after receiving upgrade file, digital signature, the contrast of kernel version, equipment Serial Number contrast and software version number inspection, the verification scheme of simple version verification is only done when optimizing modprobe order upgrading driver module, in addition, also add reduction mechanism when upgrading occurs wrong, thus improve stability and the reliability of system further.
One of ordinary skill in the art will appreciate that all or part of flow process realized in above-described embodiment method, that the hardware that can carry out instruction relevant by computer program has come, described program can be stored in a computer read/write memory medium, this program, when performing, can comprise the flow process of the embodiment as above-mentioned each side method.Wherein, described storage medium can be magnetic disc, CD, read-only store-memory body (Read-OnlyMemory, ROM) or random store-memory body (RandomAccessMemory, RAM) etc.
Above disclosedly be only present pre-ferred embodiments, certainly can not limit the interest field of the present invention with this, therefore according to the equivalent variations that the claims in the present invention are done, still belong to the scope that the present invention is contained.
Claims (10)
1. based on a driver module upgrade method for linux system, it is characterized in that, described method comprises:
Receive driver module upgrade, determine prototype version and the upgraded version of the target drives module that described driver module upgrade is corresponding;
The Depending module obtaining described target drives module and the dependence existed between described target drives module and described Depending module;
According to described dependence, unload the prototype version of described target drives module and described Depending module;
According to described dependence, be loaded into the upgraded version of described target drives module and described Depending module.
2., as claimed in claim 1 based on the driver module upgrade method of linux system, it is characterized in that, described method also comprises:
When detecting that the upgraded version of described target drives module is loaded into mistake, be again loaded into the prototype version of described target drives module and described Depending module according to described dependence.
3. as claimed in claim 1 based on the driver module upgrade method of linux system, it is characterized in that, describedly determine that the prototype version of target drives module that described driver module upgrade is corresponding and the step of upgraded version comprise:
Whether the prototype version detecting described target drives module exists;
If not, the upgraded version of described target drives module is loaded into;
If so, the Depending module performing described acquisition described target drives module and the step of dependence existed between described target drives module and described Depending module.
4. as claimed in claim 1 based on the driver module upgrade method of linux system, it is characterized in that, describedly determine that the prototype version of target drives module that described driver module upgrade is corresponding and the step of upgraded version comprise:
Receive the upgrade file of described target drives module corresponding to described driver module upgrade, check information is comprised in described upgrade file, the check information of described upgrade file is verified, if verification is passed through, then using the upgraded version of described upgrade file as described target drives module.
5. as claimed in claim 1 based on the driver module upgrade method of linux system, it is characterized in that, the Depending module of described acquisition described target drives module and the step of dependence existed between described target drives module and described Depending module comprise:
Whether the Depending module detecting described target drives module exists;
If not, unload the prototype version of described target drives module, be loaded into the upgraded version of described target drives module;
If so, perform according to described dependence, unload the prototype version of described target drives module and the step of described Depending module.
6. based on a driver module update device for linux system, it is characterized in that, described device comprises:
Target determination module, for receiving driver module upgrade, determines prototype version and the upgraded version of the target drives module that described driver module upgrade is corresponding;
Rely on acquisition module, for the Depending module that obtains described target drives module and the dependence existed between described target drives module and described Depending module;
Unload module, for according to described dependence, unloads the prototype version of described target drives module and described Depending module;
Upgraded module, for according to described dependence, is loaded into the upgraded version of described target drives module and described Depending module.
7., as claimed in claim 6 based on the driver module update device of linux system, it is characterized in that, described device also comprises:
Recovery module, for when detecting that the upgraded version of described target drives module is loaded into mistake, is loaded into the prototype version of described target drives module and described Depending module again according to described dependence.
8., as claimed in claim 6 based on the driver module update device of linux system, it is characterized in that, described target determination module also for:
Whether the prototype version detecting described target drives module exists;
If not, the upgraded version of described target drives module is loaded into;
If so, described dependence acquisition module is called.
9., as claimed in claim 6 based on the driver module update device of linux system, it is characterized in that, described target determination module is used for:
Receive the upgrade file of described target drives module corresponding to described driver module upgrade, check information is comprised in described upgrade file, the check information of described upgrade file is verified, if verification is passed through, then using the upgraded version of described upgrade file as described target drives module.
10., as claimed in claim 6 based on the driver module update device of linux system, it is characterized in that, described dependence acquisition module also for:
Whether the Depending module detecting described target drives module exists;
If not, unload the prototype version of described target drives module, be loaded into the upgraded version of described target drives module;
If so, described Unload module is called.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510708566.4A CN105278993B (en) | 2015-10-27 | 2015-10-27 | A kind of drive module upgrade method and device based on linux system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510708566.4A CN105278993B (en) | 2015-10-27 | 2015-10-27 | A kind of drive module upgrade method and device based on linux system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105278993A true CN105278993A (en) | 2016-01-27 |
| CN105278993B CN105278993B (en) | 2018-10-19 |
Family
ID=55148048
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510708566.4A Active CN105278993B (en) | 2015-10-27 | 2015-10-27 | A kind of drive module upgrade method and device based on linux system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105278993B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020108183A1 (en) * | 2018-11-30 | 2020-06-04 | 中兴通讯股份有限公司 | Method, apparatus and device for generating differential upgrade package |
| CN114116032A (en) * | 2021-11-22 | 2022-03-01 | 康佳集团股份有限公司 | WiFi module hybrid adaptive processing method, device, terminal and medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102006332A (en) * | 2010-12-03 | 2011-04-06 | 杭州华三通信技术有限公司 | Method and system for software upgrading |
| CN102135896A (en) * | 2011-03-17 | 2011-07-27 | 中兴通讯股份有限公司 | Method and system for realizing software upgrading based on embedded system |
| CN102262544A (en) * | 2010-05-24 | 2011-11-30 | 腾讯科技（深圳）有限公司 | Method and device for upgrading software |
| CN102591683A (en) * | 2011-12-28 | 2012-07-18 | 睿成汇商科技有限公司 | Updating method and updating system for embedded operation system |
| US20120317292A1 (en) * | 2007-06-12 | 2012-12-13 | International Business Machines Corporation | Managing Computer Resources in a Distributed Computing System |
| CN103077041A (en) * | 2011-07-12 | 2013-05-01 | 株式会社理光 | Communication device and update method |
| CN104182239A (en) * | 2013-05-21 | 2014-12-03 | 艾默生网络能源有限公司 | Upgrading method and upgrading device for file system based on embedded Linux equipment |
-
2015
- 2015-10-27 CN CN201510708566.4A patent/CN105278993B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120317292A1 (en) * | 2007-06-12 | 2012-12-13 | International Business Machines Corporation | Managing Computer Resources in a Distributed Computing System |
| CN102262544A (en) * | 2010-05-24 | 2011-11-30 | 腾讯科技（深圳）有限公司 | Method and device for upgrading software |
| CN102006332A (en) * | 2010-12-03 | 2011-04-06 | 杭州华三通信技术有限公司 | Method and system for software upgrading |
| CN102135896A (en) * | 2011-03-17 | 2011-07-27 | 中兴通讯股份有限公司 | Method and system for realizing software upgrading based on embedded system |
| CN103077041A (en) * | 2011-07-12 | 2013-05-01 | 株式会社理光 | Communication device and update method |
| CN102591683A (en) * | 2011-12-28 | 2012-07-18 | 睿成汇商科技有限公司 | Updating method and updating system for embedded operation system |
| CN104182239A (en) * | 2013-05-21 | 2014-12-03 | 艾默生网络能源有限公司 | Upgrading method and upgrading device for file system based on embedded Linux equipment |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020108183A1 (en) * | 2018-11-30 | 2020-06-04 | 中兴通讯股份有限公司 | Method, apparatus and device for generating differential upgrade package |
| CN114116032A (en) * | 2021-11-22 | 2022-03-01 | 康佳集团股份有限公司 | WiFi module hybrid adaptive processing method, device, terminal and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105278993B (en) | 2018-10-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10289490B2 (en) | Method and apparatus for facilitating storage system recovery and relevant storage system | |
| US8751783B2 (en) | Booting computing devices with EFI aware operating systems | |
| CN103150231B (en) | The method of computer booting and computer system | |
| US20090094450A1 (en) | Firmware image update and management | |
| CN105094927B (en) | A kind of device firmware upgrade method and apparatus | |
| CN104834575A (en) | Firmware recovery method and device | |
| CN106775610B (en) | Electronic equipment starting method and electronic equipment | |
| CN102929665B (en) | For the system of drive installation | |
| CN112015447B (en) | System updating method and device of electronic equipment, electronic equipment and storage medium | |
| CN106201640A (en) | A kind of method and device of BootLoader program of upgrading | |
| CN114780019A (en) | Electronic device management method and device, electronic device and storage medium | |
| CN105278993A (en) | Linux system based drive module upgrading method and apparatus | |
| CN112015587B (en) | Method and device for enhancing reliability of operating system | |
| CN108920338A (en) | A kind of method and terminal indicating file system state | |
| CN106445737B (en) | Multi-backup starting method | |
| KR101252358B1 (en) | Apparatus and method for testing plc command | |
| CN113272785B (en) | Method for mounting file system, terminal equipment and storage medium | |
| WO2021012170A1 (en) | Firmware booting method and device, and computer-readable storage medium | |
| CN114546537B (en) | Starting sequence deployment method and related device for multiple operating systems | |
| CN116521405A (en) | sd card state detection method, device, equipment and storage medium | |
| CN106951276B (en) | Multi-controller software upgrading and address conflict detection method and device | |
| CN115766429A (en) | Matching method and device of system and edge computing gateway | |
| CN115509618A (en) | Drive control method, device, apparatus, storage medium, and program product | |
| CN113010195B (en) | System upgrading method, storage medium and terminal equipment | |
| CN114296764A (en) | System upgrading method and device, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |