CN105278993B - A kind of drive module upgrade method and device based on linux system - Google Patents
A kind of drive module upgrade method and device based on linux system Download PDFInfo
- Publication number
- CN105278993B CN105278993B CN201510708566.4A CN201510708566A CN105278993B CN 105278993 B CN105278993 B CN 105278993B CN 201510708566 A CN201510708566 A CN 201510708566A CN 105278993 B CN105278993 B CN 105278993B
- Authority
- CN
- China
- Prior art keywords
- module
- target drives
- dependence
- depending
- version
- 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.)
- Active
Links
Landscapes
- Stored Programmes (AREA)
Abstract
The drive module upgrade method based on linux system that the invention discloses a kind of, the method includes：Drive module upgrade command is received, determines the original version and upgraded version of the corresponding target drives module of the drive module upgrade command；Obtain existing dependence between the Depending module and the target drives module and the Depending module of the target drives module；According to the dependence, the original version of the target drives module and the Depending module are unloaded；According to the dependence, it is loaded into the upgraded version of the target drives module and the Depending module.The present invention also provides a kind of drive module update device based on linux system.Using the present invention, the drive module upgrade problem in Linux system, and then the stability and reliability of lifting system can be optimized.
Description
Technical field
The present invention relates to electronic technology field more particularly to a kind of drive module upgrade method based on linux system and
Device.
Background technology
Set-top box based on (SuSE) Linux OS needs the drive module for first unloading legacy version when updating drive module
Reload the drive module of new version, if the drive module of legacy version also relies on other modules, also need to unloading with
The drive module of legacy version has the module of dependence.When being loaded into new version, it is also necessary to have according to dependence suitable
The drive module and its Depending module of the loading new version of sequence.In the prior art, Linux command provides a kind of modprobe lives
It enables, the automatic decision sequencing to be insmoded and corresponding mould can be loaded into order with modprobe
Block.
But the versatility of modprobe orders is insufficient, in the Linux system much cut, can not all use
Modprobe orders are caused when updating drive module, and drive module just can not be unloaded and be loaded into the correct order,
It may result in the need for restarting set-top box to initialize drive module, even resulting in drive module can not run, to cause system
What is run is unstable, influences the reliability of system.On the other hand, modprobe orders need fixedly save file, that is, need
Certain space and dependence are destroyed or produce the unsuccessful correctness that can influence drive module if relied on.
Invention content
Technical problem to be solved of the embodiment of the present invention is, provides a kind of drive module liter based on linux system
Grade method and device, to optimize the drive module upgrade problem in Linux system, and then the stability of lifting system and can
By property.
The drive module upgrade method based on linux system that an embodiment of the present invention provides a kind of, this method include：
Drive module upgrade command is received, determines the original of the corresponding target drives module of the drive module upgrade command
Version and upgraded version；
Between the Depending module and the target drives module and the Depending module that obtain the target drives module
Existing dependence；
According to the dependence, the original version of the target drives module and the Depending module are unloaded；
According to the dependence, it is loaded into the upgraded version of the target drives module and the Depending module.
Correspondingly, the embodiment of the present invention additionally provides a kind of drive module update device based on linux system, the device
Including：
Target determination module determines that the drive module upgrade command is corresponding for receiving drive module upgrade command
The original version and upgraded version of target drives module；
Rely on acquisition module, Depending module and the target drives module for obtaining the target drives module with
Existing dependence between the Depending module；
Unload module, original version for according to the dependence, unloading the target drives module and described
Depending module；
Upgraded module, upgraded version for according to the dependence, being loaded into the target drives module and described
Depending module.
Depending module and target drives module and dependence of the embodiment of the present invention according to the target drives module got
Existing dependence between module, unloads the original version and Depending module of target drives module, and is loaded into target drive
The upgraded version and Depending module of dynamic model block can optimize the drive module upgrade problem in Linux system, and then promote system
The stability and reliability of system.
Description of the drawings
In order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, to embodiment or will show below
There is attached drawing needed in technology description to be briefly described, it should be apparent that, the accompanying drawings in the following description is only this
Some embodiments of invention for those of ordinary skill in the art without creative efforts, can be with
Obtain other attached drawings according to these attached drawings.
Fig. 1 is a kind of flow diagram of the drive module upgrade method based on linux system in the embodiment of the present invention；
Fig. 2 is a kind of composite structural diagram of the drive module update device based on linux system in the embodiment of the present invention；
Fig. 3 is the schematic diagram of a kind of drive module and the dependency tiee of Depending module in the embodiment of the present invention；
Fig. 4 is the schematic diagram of a kind of drive module and the dependency tiee of Depending module in the embodiment of the present invention.
Specific implementation mode
Following will be combined with the drawings in the embodiments of the present invention, and technical solution in the embodiment of the present invention carries out clear, complete
Site preparation describes, it is clear that described embodiments are only a part of the embodiments of the present invention, instead of all the embodiments.It is based on
Embodiment in the present invention, those of ordinary skill in the art are obtained every other without creative efforts
Embodiment shall fall within the protection scope of the present invention.
In order to optimize the driver upgrade problem of Linux system, the embodiment of the present invention proposes a kind of based on linux system
Drive module upgrade method, this method flow may rely on the implementation of the computer program based on linux system, the computer journey
Sequence can run on the computer system of von Neumann system, which can be the machine top with linux system
Box, smart television etc..Fig. 1 is that a kind of flow of the drive module upgrade method based on linux system is shown in the embodiment of the present invention
It is intended to, the method as shown in the figure includes at least：
Step S101 receives drive module upgrade command, determines the corresponding target drives of the drive module upgrade command
The original version and upgraded version of module.
Specifically, the drive module that target drives module, which is user, to be selected, the original version of goal drive module
And upgraded version, essence is also all target drives module.The original version of target drives module can refer to target drives mould
The upgraded version of the block version currently in use not upgraded also, target drives module can be user specifies, set-top box detection
It is out or being received from other-end compared with the newer version of original version, it may also be said to, be to the leakage in original version
The improvement of hole and defect and the version after optimization.
In the present embodiment, then user can select the original version of the target drives module with selection target drive module
This and upgraded version, click determine that then set-top box receives the drive module upgrade command to trigger drive module upgrade command
Afterwards, you can determine target drives module and the original version and upgraded version of the target drives mould.In another embodiment,
Set-top box can also be after user triggers the drive module upgrade command for target drives module, and intelligent detection simultaneously obtains mesh
Mark the corresponding original version of drive module and upgraded version.
It should be noted that when set-top box obtains the corresponding original version of target drives module and upgraded version, if
Upgraded version has stored in set-top box, then set-top box directly acquires upgraded version；If upgraded version is not present in
In set-top box, then set-top box can be to the upgraded version of reception target drives module after other-end or server request.
Step S102 obtains Depending module and the target drives module and the dependence of the target drives module
Existing dependence between module.
Specifically, the startup that dependence can refer to a certain service needs with the presence of another service and starts as item
Part.For example, A services are serviced dependent on B, when needing to start A services, B services there must be and be starting state, otherwise
A services can not start.The relationship as A and B can be known as dependence, i.e. A services are serviced dependent on B.
In the present embodiment, the Depending module of target drives module can refer to has dependence with target drives module
Module, then feeling the pulse with the finger-tip mark drive module depends on this kind of relationship that its Depending module just can start or run to dependence.Machine top
Box is after determining target drives module, you can the Depending module and target drives module of acquisition target drives module and dependence
Existing dependence between module.
In specific implementation, target drives module can not have Depending module, it is possibility to have multiple Depending modules.When target is driven
When dynamic model block has multiple Depending modules, the dependence between the target drives module that set-top box obtains and its Depending module is practical
On be the equal of target drives module and its Depending module dependency tiee.Dependency tiee as shown in Figure 3, if A is mesh
Drive module is marked, A is respectively connected with B, C, D means that A respectively depends on B Depending modules, C Depending modules and D Depending modules.
Further, the Depending module of target drives module can also have the module that there is dependence therewith, then can be with
According to the dependence between each module, more complete dependency tiee is obtained.Dependency tiee as shown in Figure 4, can be with
Find out that the dependence for being easy to obtain between A~G is：A depends on B, C, D, B that E, F, F is depended on to again rely on G.
Step S103 unloads the original version of the target drives module and the dependence according to the dependence
Module.
Specifically, in order to be loaded into the upgraded version of target drives module, set-top box will first unload the original of target drives module
Beginning version, and when target drives module is there are when Depending module, then also the Depending module of target drives module is also unloaded
The loading of the upgraded version and Depending module of target drives module could be completed later.
In specific implementation, existing dependence between target drives module and Depending module is got in step s 102
Afterwards, set-top box can have the original version and Depending module for sequentially unloading target drives module according to dependence.
That is target drives module depends on Depending module, after set-top box then can first unload the original version of target drives module,
Depending module is unloaded again.
When target drives module is there are when multiple Depending modules, if the dependence between Depending module and target drives module
Relationship is parallel, that is, is at the Depending module with first nodes in the dependency tiee of target drives module, and rely on
Module also has no dependence from each other, then set-top box can unload all Depending modules according to random order.
For example, dependency tiee as shown in Figure 3, B, C, D are all in the same first nodes of dependency tiee, then set-top box
It after having unloaded A, can be unloaded since B, then unload C and D successively, can also successively be unloaded with the sequence of C, D, B, it can be with
Unloaded successively with the sequence of D, C, B etc..
Further, when the Depending module of target drives module also has the module that there is dependence therewith, set-top box
Can according to the dependency tiee got, according to the sequence that highest node is unloaded to lowermost level node in dependency tiee,
The original version and Depending module of target drives module are unloaded successively.
For example, dependency tiee as shown in Figure 4, A is in dependency tiee highest node, and G is in dependence
Lowermost level node in tree, then set-top box can be unloaded since A, then unload B, C, D, then unload E and F, finally unload G.
Step S104 is loaded into the upgraded version of the target drives module and the dependence according to the dependence
Module.
Specifically, since target drives module depends on Depending module that could run or start, it is driven being loaded into target
When the upgraded version of dynamic model block, also the Depending module of target drives module is loaded into together.
In specific implementation, loading sequence can be got according in step S102 between target drives module and Depending module
Existing dependence has the original version and Depending module for being sequentially loaded into target drives module.That is, target is driven
Dynamic model block depends on Depending module, after set-top box then first can be loaded into Depending module, reloads the upgrade version of target drives module
This.
When target drives module is there are when multiple Depending modules, if the dependence between Depending module and target drives module
Relationship is parallel, that is, is at the Depending module with first nodes in the dependency tiee of target drives module, and rely on
Module also has no dependence from each other, then set-top box can be loaded into all Depending modules according to random order, be finally loaded
The upgraded version of target drives module.
For example, dependency tiee as shown in Figure 3, B, C, D are all in the same first nodes of dependency tiee, then set-top box
It can be loaded into since B, then be loaded into C and D successively, can also be successively loaded into the sequence of C, D, B, it can also be with D, C, B
Sequence loading etc. successively, after B, C, D are loaded into, reloads A.
Further, when the Depending module of target drives module also has the module that there is dependence therewith, set-top box
Can according to the dependency tiee got, according to the sequence that lowermost level node is loaded into highest node in dependency tiee,
It is finally loaded the upgraded version of target drives module.
For example, dependency tiee as shown in Figure 4, G is in lowermost level node in dependency tiee, then set-top box can be from
G starts to be loaded into, and is then loaded into E and F, reloads B, C, D, be finally loaded A.
In an alternative embodiment, when detecting that the upgraded version of the target drives module is loaded into mistake, according to described
Dependence is loaded into the original version of the target drives module and the Depending module again.
Specifically, when step S104 occurs being loaded into mistake, target drives module is just unable to operate normally.At this point, machine top
Box can be loaded into the original version and Depending module of target drives module again according to the dependence.It needs to illustrate
It is that the original version of target drives module can be set-top box unloading but be stored in the case of not deleting its file here
, it can also be the pre-stored backup file of set-top box, be not especially limited here.
In specific implementation, loading method and the loading method in step S104 are almost the same, i.e., according in step S102
The dependence of acquisition is loaded into target and drives again successively according to the sequence for being loaded into target drives module after Depending module is first loaded into
The original version and Depending module of dynamic model block.
In another alternative embodiment, step S101 further includes：It is corresponding described to receive the drive module upgrade command
The upgrade file of target drives module includes check information in the upgrade file, to the check information of the upgrade file into
Row verification, if verification passes through, using the upgrade file as the upgraded version of the target drives module.
Specifically, after user inputs drive module upgrade command, set-top box can have connection relation to set-top box
Server or other-end device request obtain target drives module upgrade file.The upgrade file of target drives module
Binary file is could be provided as, wherein cyclic redundancy check code (CRC), digital signature, kernel version, equipment sequence can be carried
The check informations such as row number and software version number.It, can be to upgrading after set-top box receives the upgrade file of target drives module
File carries out CRC check and the comparison of digital signature, kernel version, equipment Serial Number and software version number is checked and approved, if verification
Pass through, then illustrate that upgrade file is errorless, i.e., the upgrade file that set-top box receives is sent with server or other-end equipment
Upgrade file be consistent, then upgrade file can be determined as the upgraded version of target drives module by set-top box.
For example, having the server or other-end equipment of connection relation with set-top box, according to the upgrade file to be transmitted
The positions k binary message code, a r CRC codes are generated with default rule and are attached to k binary message code back, composition one
A new upgrade file with total k+r of binary message code is sent to set-top box.After set-top box receives upgrade file,
It can be tested according to the preset rules followed between binary message code and CRC code, to determine in transmission whether malfunction.
In another example set-top box by the digital signature received, kernel version, equipment Serial Number and software version number with it is corresponding
The digital signature being pre-stored in set-top box, kernel version, equipment Serial Number and software version number be compared, if comparing it
Afterwards, corresponding check information is all consistent, it is determined that transmission is errorless, otherwise, illustrates that the upgrade file does not meet the set-top box and wants
The upgrade file verification attribute asked.
In another alternative embodiment, step S101 further includes：Detect the target drives module original version whether
In the presence of if it is not, being loaded into the upgraded version of the target drives module；If so, executing step S102.
Specifically, before set-top box gets the corresponding original version of target drives module, target drive can be first detected
The original version of dynamic model block whether there is.
If being found after detection, the original version of target drives module is not present, can be directly by the liter of target drives module
Grade version is loaded into set-top box, without the step of being reloaded after being unloaded again to the original version of target drives module.
It further, can be with if with target drives module there are the Depending module of dependence in the upgraded version of target drives module
First Depending module is loaded into, then the upgraded version of target drives module is loaded into set-top box.
If detecting, the original version of target drives module exists, and thens follow the steps S102.
In another alternative embodiment, step S102 further includes：Detect the target drives module Depending module whether
In the presence of, if it is not, unloading the original version of the target drives module, it is loaded into the upgraded version of the target drives module, if so,
Execute step S103.
Specifically, set-top box obtain target drives module Depending module and target drives module and Depending module it
Between before existing dependence, the Depending module that can first detect target drives module whether there is.
If detection after find target drives module Depending module be not present namely target drives module and without rely on its
His module starts or runs, then can directly unload the original version of target drives module, is loaded into target drives module
Upgraded version, the original without going unloading target drives module further according to the dependence of target drives module and Depending module
Beginning version or the upgraded version for being loaded into target drives module.
If detecting, the Depending module of target drives module exists, and thens follow the steps S103.
Depending module and target drives module and dependence of the embodiment of the present invention according to the target drives module got
Existing dependence between module has the original version and Depending module for sequentially unloading target drives module, and root
According to dependence, there are the upgraded version and Depending module for being sequentially loaded into target drives module, to complete target drives mould
The upgrading of block, can optimize the drive module upgrade problem in Linux system, and then the stability of lifting system and reliable
Property.Further, present invention also adds the CRC check after reception upgrade file, digital signature, kernel version comparison, equipment
Sequence number compares and software version number inspection, and simple version verification is only done when optimizing modprobe orders upgrading drive module
Verification scheme, in addition, upgrading reduction mechanism when the error occurs is also added, to further improve the stability of system
And reliability.
In order to optimize the driver upgrade problem of Linux system, the embodiment of the present invention correspondingly proposes a kind of based on Linux
The drive module update device of system, the device include：Target determination module 210 relies on acquisition module 220, Unload module 230
And upgraded module 240, wherein：
Target determination module 210 determines that the drive module upgrade command corresponds to for receiving drive module upgrade command
Target drives module original version and upgraded version.
In one embodiment, target determination module 210 is additionally operable to：Detecting the original version of the target drives module is
No presence, if it is not, the upgraded version of the target drives module is loaded into, if so, calling the dependence acquisition module 220.
In one embodiment, target determination module 210 is additionally operable to：Receive the corresponding institute of the drive module upgrade command
The upgrade file of target drives module is stated, includes check information in the upgrade file, to the check information of the upgrade file
It is verified, if verification passes through, using the upgrade file as the upgraded version of the target drives module.
Rely on acquisition module 220, the Depending module for obtaining the target drives module and the target drives mould
Existing dependence between block and the Depending module.
In one embodiment, acquisition module 220 is relied on to be additionally operable to：Detecting the Depending module of the target drives module is
No presence is loaded into the upgraded version of the target drives module if it is not, unloading the original version of the target drives module, if
It is to call the Unload module 230.
Unload module 230, for according to the dependence, unloading original version and the institute of the target drives module
State Depending module.
Upgraded module 240, for according to the dependence, being loaded into upgraded version and the institute of the target drives module
State Depending module.
Optionally, which further includes：Recovery module 250, for when the upgraded version load for detecting the drive module
When entering mistake, the original version of the target drives module and the Depending module are loaded into according to the dependence again.
Depending module and target drives module and dependence of the embodiment of the present invention according to the target drives module got
Existing dependence between module has the original version and Depending module for sequentially unloading target drives module, and root
According to dependence, there are the upgraded version and Depending module for being sequentially loaded into target drives module, to complete target drives mould
The upgrading of block, can optimize the drive module upgrade problem in Linux system, and then the stability of lifting system and reliable
Property.Further, present invention also adds the CRC check after reception upgrade file, digital signature, kernel version comparison, equipment
Sequence number compares and software version number inspection, and simple version verification is only done when optimizing modprobe orders upgrading drive module
Verification scheme, in addition, upgrading reduction mechanism when the error occurs is also added, to further improve the stability of system
And reliability.
One of ordinary skill in the art will appreciate that realizing all or part of flow in above-described embodiment method, being can be with
Relevant hardware is instructed to complete by computer program, the program can be stored in a computer read/write memory medium
In, the program is when being executed, it may include such as the flow of the embodiment of above-mentioned each method.Wherein, the storage medium can be magnetic
Dish, CD, read-only memory (Read-Only Memory, ROM) or random access memory (Random Access
Memory, RAM) etc..
The above disclosure is only the preferred embodiments of the present invention, cannot limit the right model of the present invention with this certainly
It encloses, therefore equivalent changes made in accordance with the claims of the present invention, is still within the scope of the present invention.
Claims (8)
1. a kind of drive module upgrade method based on linux system, which is characterized in that the method includes：
Drive module upgrade command is received, determines the original version of the corresponding target drives module of the drive module upgrade command
And upgraded version；
It obtains between the Depending module and the target drives module and the Depending module of the target drives module and exists
Dependence, the dependence be the target drives module dependent on its Depending module just can start or run should
Kind relationship；
According to the dependence, the original version of the target drives module and the Depending module are unloaded；
According to the dependence, it is loaded into the upgraded version of the target drives module and the Depending module；
Wherein, the original version and upgraded version of the corresponding target drives module of the determination drive module upgrade command
Step includes：
The original version for detecting the target drives module whether there is；
If it is not, being loaded into the upgraded version of the target drives module；
If so, executing the Depending module for obtaining the target drives module and the target drives module and the dependence
Between module the step of existing dependence.
2. the drive module upgrade method based on linux system as described in claim 1, which is characterized in that the method is also
Including：
When detect the target drives module upgraded version be loaded into mistake when, be loaded into again according to the dependence described in
The original version of target drives module and the Depending module.
3. the drive module upgrade method based on linux system as described in claim 1, which is characterized in that the determining institute
The step of original version and upgraded version for stating the corresponding target drives module of drive module upgrade command includes：
The upgrade file of the corresponding target drives module of the drive module upgrade command is received, is wrapped in the upgrade file
Containing check information, the check information of the upgrade file is verified, if verification passes through, using the upgrade file as institute
State the upgraded version of target drives module.
4. the drive module upgrade method based on linux system as described in claim 1, which is characterized in that the acquisition institute
State existing dependence between the Depending module and the target drives module and the Depending module of target drives module
The step of include：
The Depending module for detecting the target drives module whether there is；
If it is not, unloading the original version of the target drives module, it is loaded into the upgraded version of the target drives module；
If so, executing according to the dependence, the original version of the target drives module and the Depending module are unloaded
The step of.
5. a kind of drive module update device based on linux system, which is characterized in that described device includes：
Target determination module determines the corresponding target of the drive module upgrade command for receiving drive module upgrade command
The original version and upgraded version of drive module；
Rely on acquisition module, Depending module and the target drives module for obtaining the target drives module with it is described
Existing dependence between Depending module, the dependence are that the target drives module just may be used dependent on its Depending module
With this kind of relationship for starting or running；
Unload module, for according to the dependence, unloading the original version of the target drives module and the dependence
Module；
Upgraded module, for according to the dependence, being loaded into the upgraded version of the target drives module and the dependence
Module；
Wherein, the target determination module is additionally operable to：
The original version for detecting the target drives module whether there is；
If it is not, being loaded into the upgraded version of the target drives module；
If so, calling the dependence acquisition module.
6. the drive module update device based on linux system as claimed in claim 5, which is characterized in that described device is also
Including：
Recovery module, for when detecting that the upgraded version of the target drives module is loaded into mistake, being closed according to the dependence
System is loaded into the original version of the target drives module and the Depending module again.
7. the drive module update device based on linux system as claimed in claim 5, which is characterized in that the target is true
Cover half block is used for：
The upgrade file of the corresponding target drives module of the drive module upgrade command is received, is wrapped in the upgrade file
Containing check information, the check information of the upgrade file is verified, if verification passes through, using the upgrade file as institute
State the upgraded version of target drives module.
8. the drive module update device based on linux system as claimed in claim 5, which is characterized in that the dependence obtains
Modulus block is additionally operable to：
The Depending module for detecting the target drives module whether there is；
If it is not, unloading the original version of the target drives module, it is loaded into the upgraded version of the target drives module；
If so, calling the Unload module.
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 CN105278993A (en) | 2016-01-27 |
| CN105278993B true 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) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111258620B (en) * | 2018-11-30 | 2022-02-22 | 中兴通讯股份有限公司 | Method, device and equipment for generating differential upgrade package |
| CN114116032A (en) * | 2021-11-22 | 2022-03-01 | 康佳集团股份有限公司 | WiFi module hybrid adaptive processing method, device, terminal and medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102135896A (en) * | 2011-03-17 | 2011-07-27 | 中兴通讯股份有限公司 | Method and system for realizing software upgrading based on embedded system |
| 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 |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8266287B2 (en) * | 2007-06-12 | 2012-09-11 | International Business Machines Corporation | Managing computer resources in a distributed computing system |
| CN102262544B (en) * | 2010-05-24 | 2016-06-08 | 腾讯科技（深圳）有限公司 | The method and apparatus of software upgrading |
| CN102006332B (en) * | 2010-12-03 | 2013-12-11 | 杭州华三通信技术有限公司 | Method and system for software upgrading |
| JP5790222B2 (en) * | 2011-07-12 | 2015-10-07 | 株式会社リコー | Communication device, update method, and update program |
-
2015
- 2015-10-27 CN CN201510708566.4A patent/CN105278993B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102135896A (en) * | 2011-03-17 | 2011-07-27 | 中兴通讯股份有限公司 | Method and system for realizing software upgrading based on embedded system |
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105278993A (en) | 2016-01-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8683457B1 (en) | Updating firmware of an electronic device by storing a version identifier in a separate header | |
| US8751783B2 (en) | Booting computing devices with EFI aware operating systems | |
| CN104156244A (en) | Method and device for software upgrading | |
| CN110442473B (en) | Nonvolatile data storage method and device, electronic equipment and medium | |
| WO2016183951A1 (en) | System upgrade method and terminal | |
| US7418589B2 (en) | System and method for updating a basic input/output system | |
| CN106897166B (en) | Mobile terminal and repairing method thereof | |
| US7127596B2 (en) | Method and system for improving computer system boot reliability by executing an application specific test during a boot prior loading an operating system | |
| CN106201640A (en) | A kind of method and device of BootLoader program of upgrading | |
| CN106648685A (en) | Processing method and device of intelligent terminal system and intelligent terminal | |
| CN112631628A (en) | Singlechip upgrading method, singlechip and storage medium | |
| CN112540725A (en) | Nonvolatile data storage method, embedded system and storage medium | |
| CN105677409B (en) | A kind of method for upgrading system and device | |
| CN110597545A (en) | Hot patch intelligent upgrading method and system based on OTA component | |
| CN109002305B (en) | Method and system for updating equipment program | |
| CN105278993B (en) | A kind of drive module upgrade method and device based on linux system | |
| CN111158968A (en) | BIOS configuration information self-checking method, device and storage medium | |
| CN114780019A (en) | Electronic device management method and device, electronic device and storage medium | |
| US20060026415A1 (en) | Method of updating a portion BIOS | |
| CN108196975B (en) | Data verification method and device based on multiple checksums and storage medium | |
| CN106445737B (en) | Multi-backup starting method | |
| US20110252414A1 (en) | System using separate modules to update software and the method thereof | |
| CN110244986B (en) | Browser configuration method and device | |
| US10691465B2 (en) | Method for synchronization of system management data | |
| WO2017143513A1 (en) | Method, cpu and single board for starting boot |
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 |