CN107423075B - Driven registration method and user terminal - Google Patents
Driven registration method and user terminal Download PDFInfo
- Publication number
- CN107423075B CN107423075B CN201710748880.4A CN201710748880A CN107423075B CN 107423075 B CN107423075 B CN 107423075B CN 201710748880 A CN201710748880 A CN 201710748880A CN 107423075 B CN107423075 B CN 107423075B
- Authority
- CN
- China
- Prior art keywords
- firmware
- equipment
- firmware parameters
- parameters
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4406—Loading of operating system
- G06F9/441—Multiboot arrangements, i.e. selecting an operating system to be loaded
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Abstract
A drive registration method and a user terminal are provided, the drive registration method comprises: initializing a driver, searching equipment corresponding to the driver and acquiring an identification code of the equipment, wherein firmware parameters of the equipment are stored in a system file; acquiring specific firmware parameters matched with the identification codes from a system file, and copying and storing the specific firmware parameters in a memory array; judging whether the equipment needs firmware upgrading; if so, writing the specific firmware parameters into a chip of the equipment, and then finishing drive registration; if not, the drive registration is directly completed. The drive registration method and the user terminal can effectively save the space of the memory and improve the system performance of the user terminal.
Description
Technical Field
The present invention relates to the field of mobile terminal technologies, and in particular, to a driven registration method and a mobile terminal.
Background
At present, the mobile phone industry is fast in updating speed, one or two mobile phones are developed in the past one year, and one or two mobile phones are developed in the present one year, and in most cases, the one or two mobile phones may adopt different intelligent platforms, such as 65XX, 67XX and 683X of a company and a company department (MTK), and the adopted hardware may also be different, such as a touch screen chip, and there are M, N, P, Q and other chip manufacturers. However, the mobile phones which may adopt different intelligent platforms and different chip manufacturers all need to adopt a set of codes for management, that is, a set of android codes must be capable of being effectively compatible with different mobile phone hardware and different mobile phone platforms, so that a very high requirement is put forward on the platform of the mobile phone. The same problem is faced on many devices such as smart televisions.
When the mobile phone is normally started, each hardware device of the mobile phone needs to be registered in the operating system, so that a user can control the hardware device to normally work through the operating system. Referring to fig. 1, a method for performing driver registration in the prior art is shown. After the mobile phone is started, the following steps are executed: s10, initializing the drive, and searching the equipment corresponding to the drive; s11: acquiring firmware parameters corresponding to the equipment in the drive codes and storing the firmware parameters in a memory array; s12: reading the equipment identification code; step S13: judging whether a firmware matched with the equipment identification code needs to be issued or not; if so, go to step S14: upgrading the device firmware, and step S15: and (5) finishing the drive registration and normally working the equipment.
However, in the prior art, incompatibility is easily caused in the process of performing system registration, for example, for a touch screen, an M chip factory uses a module (ID ═ 2) of an N module factory for an a project of the MTK67XX platform, and also uses a module (ID ═ 2) of an N module factory for a B project of the MTK67XX platform, but the two touch screens have different sizes and different routing, and corresponding firmware parameters are also different, so that a compiled code cannot judge which firmware parameter is issued to a touch screen control chip of a mobile phone, and thus the mobile phone touch screen originally in the a project normally works, while the touch screen in the B project normally does not work, otherwise, the mobile phone touch screen originally in the B project normally works, but the mobile phone touch screen in the a project cannot normally work. Moreover, since the M-chip driver firmware code is usually large, for example, 49664 bytes, and placed in hexadecimal in the driver code, the size is large, and the reading of a technician is laborious. If an M chip factory has three items in a certain platform of the MTK, memory space which is three times of 49664 bytes is required to be applied for storing the firmware, but only 49664 bytes of space of one firmware is actually required to be used, and the other two 49664 bytes of space are wasted. Further, in the prior art, different firmware parameters need to be distinguished according to different identification codes, for example, the N company 655X chip adopts a touch screen module of an N module factory, the identification code is 1, and the touch screen structure of the next N company 655X chip N module factory changes so that the identification code is 2, the firmware parameter changes greatly, and since the firmware codes are all placed in the driver codes, the touch screen driver codes are greatly modified, and the platform migration cannot be well realized.
Therefore, a new driver registration method and a mobile terminal are needed to improve the compatibility of driver registration and save memory space.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a driver registration method and a user terminal, which improve the compatibility of driver registration and save memory space.
In order to solve the above problem, the present invention provides a drive registration method, including: initializing a driver, searching equipment corresponding to the driver and acquiring an identification code of the equipment, wherein firmware parameters of the equipment are stored in a system file; acquiring specific firmware parameters matched with the identification codes from a system file, and copying and storing the specific firmware parameters in a memory array; judging whether the equipment needs firmware upgrading; if so, writing the specific firmware parameters into a chip of the equipment, and then finishing drive registration; if not, the drive registration is directly completed.
Optionally, a plurality of different firmware parameters corresponding to different identification codes are stored in the system file.
Optionally, the method further includes: and acquiring the updated firmware parameters and storing the updated firmware parameters in a system file. Optionally, the method further includes: and after the drive registration is completed, releasing the memory space occupied by the specific firmware parameters.
The technical solution of the present invention also provides a user terminal, including: the file storage module is used for storing a system file, and the system file comprises firmware parameters of equipment; the initialization module is used for initializing a drive, searching equipment corresponding to the drive in the user terminal and acquiring an identification code of the equipment; the matching module is connected with the information acquisition module and the file storage module and used for acquiring specific firmware parameters matched with the identification codes from a system file according to the identification codes and storing the specific firmware parameters in a memory array; the judging module is connected with the matching module and used for judging whether the equipment needs to be upgraded or not; and the registration module is connected with the judgment module, and is used for completing drive registration after the specific firmware parameters are written into a chip of the equipment if firmware upgrading is needed, and is used for directly completing drive registration if firmware upgrading is not needed.
Optionally, the system file includes a plurality of different firmware parameters corresponding to different identification codes.
Optionally, the method further includes: and the updating module is connected with the file storage module and used for acquiring the updated firmware parameters and storing the updated firmware parameters in a system file.
Optionally, the method further includes: and the release module is connected with the registration module and used for releasing the memory space occupied by the specific firmware parameters after the drive registration is finished.
The user terminal and the drive registration method thereof store the equipment firmware parameters in the system folder, search the equipment corresponding to the drive during drive initialization, acquire the identification code of the equipment, scan the system folder, acquire the specific firmware parameters matched with the identification code of the equipment and store the specific firmware parameters in the memory, and write the firmware parameters into the equipment chip if the firmware upgrading is needed to complete the drive registration. Only the matched specific firmware parameters need to be stored in the memory, so that the memory space of the user terminal can be effectively saved; and the firmware parameters are stored in the system file, so that the portability of the drive codes can be improved, and errors can be avoided when the firmware is issued.
Drawings
FIG. 1 is a flow chart illustrating a method for performing driver registration in the prior art;
FIG. 2 is a schematic structural diagram of a user equipment according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a user terminal according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a user terminal according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating a driver registration method according to an embodiment of the invention.
Detailed Description
The following describes in detail specific embodiments of a drive registration method and a user terminal according to the present invention with reference to the accompanying drawings.
Please refer to fig. 2, which is a schematic structural diagram of a ue according to an embodiment of the present invention.
In this embodiment, the user terminal includes: a file storage module 201, an initialization module 202, a matching module 203, a judgment module 204 and a registration module 205.
The file storage module 201 is configured to store a system file, where the system file includes firmware parameters of a device. The file storage module 201 is a system storage module of the user terminal. In a specific embodiment, the user terminal is a mobile phone, and the file storage module 201 is a Flash memory. The system file is an operating system file of the user terminal and is stored in the file storage module 201. The firmware parameters are different according to the type, size, routing and the like of the modules adopted by the equipment.
The user terminal includes a plurality of devices such as a touch screen, a camera, a microphone, and the like, the system needs to operate the devices through drivers corresponding to the devices, and each device needs firmware support so as to be controlled by a driver. When the user terminal is started, the equipment and the drive of each equipment need to be registered on a system bus to normally work. Different devices correspond to different firmware and different drivers, and can be successfully registered only by matching the devices with each other.
The firmware parameters are used for burning and upgrading the firmware of the equipment. In this embodiment, the firmware parameters are stored in the system file, rather than in the driver code, which can reduce the size of the device driver code and improve the readability of the code.
The same equipment is adopted, but different modules are adopted, and corresponding firmware parameters are different; the same equipment adopts the same module, but the corresponding firmware parameters are different on products with different models, sizes or routing lines are different. In order to improve compatibility in the prior art, for one device, a plurality of firmware parameters are usually stored in a driver code, and when the driver registers, the plurality of firmware parameters are stored in a memory at the same time, so that a problem that a compiled code cannot judge which firmware parameter is issued to a chip of the device, thereby causing the device to be incapable of working normally, easily occurs.
In the specific embodiment of the present invention, for the same device, a plurality of firmware parameters are stored in a system file, different firmware parameters correspond to different identification codes, each firmware parameter is stored in a folder of the system in a file form, the firmware parameters of different items are stored in folders corresponding to the items, for example, the firmware parameters of the module of the N module factory for the a item are stored in the folder for the a item, for example, the arch/arm/boot/dts folder of the android system, and the firmware parameters of the module of the N module factory for the B item are stored in the folder for the B item, for example, the arch/arm/boot/dts folder, so that it is convenient to find the corresponding firmware parameters during subsequent driver registration, and no error occurs.
An initialization module 202 for initializing the drive. In the process of driver registration, connection between a driver and equipment needs to be established, in the process of initializing the driver, equipment corresponding to the driver in a user terminal is searched, and an identification code of the equipment is acquired. For example, the driving of the touch screen is initialized, the touch screen corresponding to the driving in the user terminal is searched, and the identification code of the touch screen is acquired. The identification codes are used for distinguishing different modules, structures, models and the like, and the different identification codes correspond to different firmware parameters.
And the matching module 203 is connected with the information acquisition module 202 and the file storage module 201, and is used for acquiring specific firmware parameters matched with the identification codes from the system files according to the identification codes and storing the specific firmware parameters in the memory array. The matching module 203 is configured to scan a folder storing the firmware parameters in the file storage module 201 according to the identification code obtained by the information obtaining module 202, and obtain the specific firmware parameters corresponding to the identification code. All folders storing the specific firmware parameters can be scanned completely to acquire the specific firmware parameters corresponding to the identification codes.
In other specific embodiments, the file system stores a plurality of firmware parameters, and the firmware parameters are stored in different folders according to different items, for example, the device firmware parameter of the a item is stored in the folder of the a item, the device firmware parameter of the B item is stored in the folder of the B item, and when the driver of the a item is registered, the matching module 203 may only be configured to search the folder of the a item for the matched firmware parameter, so as to avoid obtaining the wrong firmware parameter. After the specific firmware parameters matched with the identification codes are obtained, the firmware parameters are copied and stored in an array of the memory, and the firmware parameters are decoded into hexadecimal codes and stored in the memory. Since the identification code is firstly identified, only one specific firmware parameter is acquired, and therefore, only the space of one firmware parameter needs to be occupied in the memory. Compared with the prior art, the method has the advantage that the occupied space of the memory can be remarkably saved by copying all firmware parameters into the memory. Moreover, the firmware parameters are stored in the system file, but not in the driver code, so when the firmware parameters are changed, the driver code does not need to be changed, and the portability of the driver code can be improved.
And the judging module 204 is connected with the matching module 203 and is used for judging whether the equipment needs to be upgraded. The user terminal writes the firmware parameters in the chip of the device after starting up and initializing every time, and carries out firmware upgrade, so that the firmware parameters written last time can be stored in the chip of the device. The determining module 204 is configured to compare the acquired specific firmware parameter with a firmware parameter written in the device chip, and if the specific firmware parameter acquired during the initialization of the driver is consistent with the version content of the firmware parameter written in the device chip, the driver can directly complete the driver registration without performing the firmware upgrade without performing the writing again, and the device can be used normally. If the obtained specific firmware parameters are inconsistent with the firmware parameters written in the chip, the equipment firmware needs to be upgraded.
The registration module 205 is connected to the determination module 204, and if firmware upgrade is required, the registration module 205 is configured to complete driver registration after writing the specific firmware parameters into a chip of the device. If the firmware upgrade is not needed, the registration module 205 is configured to directly complete the driver registration. And after the drive registration is finished and the user starts the machine, the equipment can work normally.
Please refer to fig. 3, which is a schematic structural diagram of a ue according to another embodiment of the present invention.
The user terminal further comprises an updating module 301, and the updating module 301 is connected with the file storage module 201 and the initialization module 202. When the initialization module 202 initializes the driver, the update module 301 is configured to connect to a server, obtain updated firmware parameters, and store the updated firmware parameters in a system file of the file storage module 201. Therefore, the firmware parameters can be updated each time the drive registration is carried out after the start-up. The update module 301 may obtain a plurality of firmware parameters of the same device type from the server at the same time, and store the firmware parameters in corresponding folders respectively.
Please refer to fig. 4, which is a schematic structural diagram of a ue according to another embodiment of the present invention.
The user terminal further includes: the release module 401 is connected to the registration module 205, and configured to release the memory space occupied by the specific firmware parameter after the driver registration is completed. After the drive finishes the firmware, the firmware parameter data does not need to be used, so the release module 401 is used to release the memory space occupied by the specific firmware parameter, and the specific firmware parameter data in the memory can be deleted or covered by the data subsequently written into the memory, thereby releasing the memory space, improving the practical efficiency of the memory and improving the system performance of the user terminal.
The equipment firmware parameters of the user terminal are stored in a system folder, when an initialization module carries out drive initialization, after equipment corresponding to a drive is searched, the identification code of the equipment is obtained, then the system folder is scanned through a matching module, the specific firmware parameters matched with the identification code of the equipment are obtained and stored in a memory, and if firmware upgrading is needed, the firmware parameters are written into an equipment chip to complete drive registration. Only the matched specific firmware parameters need to be stored in the memory, so that the memory space of the user terminal can be effectively saved; and the firmware parameters are stored in the system file, so that the portability of the drive codes can be improved, and errors can be avoided when the firmware is issued.
The specific implementation mode of the invention also provides a drive registration method.
Fig. 5 is a flowchart illustrating a drive registration method according to an embodiment of the present invention.
The drive registration method comprises the following steps:
step S501: initializing the driver, searching the equipment corresponding to the driver, and storing the firmware parameters of the equipment in a system file.
The system file of the user terminal includes the firmware parameters of the device. The system file may be stored in a system storage module of the user terminal. In a specific embodiment, the user terminal is a mobile phone, and the file storage module is a Flash memory. The system file is an operating system file of the user terminal and is stored in the file storage module. The firmware parameters are different according to the type, size, routing and the like of the modules adopted by the equipment.
The user terminal includes a plurality of devices such as a touch screen, a camera, a microphone, and the like, the system needs to operate the devices through drivers corresponding to the devices, and each device needs firmware support so as to be controlled by a driver. When the user terminal is started, the equipment and the drive of each equipment need to be registered on a system bus to normally work. Different devices correspond to different firmware and different drivers, and can be successfully registered only by matching the devices with each other.
The firmware parameters are used for burning and upgrading the firmware of the equipment. In this embodiment, the firmware parameters are stored in the system file, rather than in the driver code, which can reduce the size of the device driver code and improve the readability of the code.
The same equipment is adopted, but different modules are adopted, and corresponding firmware parameters are different; the same equipment adopts the same module, but the corresponding firmware parameters are different on products with different models, sizes or routing lines are different. In order to improve compatibility in the prior art, for one device, a plurality of firmware parameters are usually stored in a driver code, and when the driver registers, the plurality of firmware parameters are stored in a memory at the same time, so that a problem that a compiled code cannot judge which firmware parameter is issued to a chip of the device, thereby causing the device to be incapable of working normally, easily occurs.
In the specific embodiment of the present invention, for the same device, a plurality of firmware parameters are stored in a system file, different firmware parameters correspond to different identification codes, each firmware parameter is stored in a folder of the system in a file form, the firmware parameters of different items are stored in folders corresponding to the items, for example, the firmware parameters of the module of the N module factory for the a item are stored in the folder for the a item, for example, the arch/arm/boot/dts folder of the android system, and the firmware parameters of the module of the N module factory for the B item are stored in the folder for the B item, for example, the arch/arm/boot/dts folder, so that it is convenient to find the corresponding firmware parameters during subsequent driver registration, and no error occurs.
The method comprises the steps that a user terminal needs to be driven and registered in the starting process, connection between a driver and equipment is established, equipment corresponding to the driver in the user terminal is searched in the driving initialization process, and the identification code of the equipment is obtained. For example, the driving of the touch screen is initialized, and the touch screen corresponding to the driving in the user terminal is searched.
Step S502: a device identification code is obtained. The identification codes are used for distinguishing different modules, structures, models and the like, the different identification codes correspond to different firmware parameters, and each device is provided with an identification code so as to correspond to a specific firmware parameter.
Step S503: and acquiring the specific firmware parameters matched with the identification codes from the system file, and copying and storing the specific firmware parameters in the memory array. And scanning a folder for storing the firmware parameters in the system file according to the obtained identification code, and obtaining the specific firmware parameters corresponding to the identification code. All folders storing the specific firmware parameters can be scanned completely to acquire the specific firmware parameters corresponding to the identification codes. In another specific embodiment, the file system stores a plurality of firmware parameters, and stores the firmware parameters in different folders according to different items, for example, the device firmware parameter of the a item is stored in the folder of the a item, the device firmware parameter of the B item is stored in the folder of the B item, and when the driver of the a item is registered, the file system may be only used to search the folder of the a item for the matched firmware parameter, thereby avoiding obtaining the wrong firmware parameter. After the specific firmware parameters matched with the identification codes are obtained, the firmware parameters are copied and stored in an array of the memory, and the firmware parameters are decoded into hexadecimal codes and stored in the memory. Since the identification code is firstly identified, only one specific firmware parameter is acquired, and therefore, only the space of one firmware parameter needs to be occupied in the memory. Compared with the prior art, the method has the advantage that the occupied space of the memory can be remarkably saved by copying all firmware parameters into the memory.
Step S504: and judging whether the equipment needs firmware upgrade.
The user terminal writes the firmware parameters in the chip of the device after starting up and initializing every time, and carries out firmware upgrade, so that the firmware parameters written last time can be stored in the chip of the device. And comparing the acquired specific firmware parameters with the firmware parameters written in the equipment chip, and if the specific firmware parameters acquired during the drive initialization are consistent with the version contents of the firmware parameters written in the equipment chip, the driver can directly complete drive registration without writing again and updating the firmware, so that the equipment can be used normally. If the obtained specific firmware parameters are inconsistent with the firmware parameters written in the chip, the equipment firmware needs to be upgraded.
If the firmware upgrade is needed, step S505 is executed to continue: and (4) firmware upgrading, specifically writing specific firmware parameters into a chip of the equipment to finish firmware upgrading. Then, step S506 is executed: and finishing the drive registration.
If the firmware upgrade is not needed, step S506 may be directly executed: and finishing the drive registration.
In the embodiment of the present invention, in step S501, when initializing the driver, the driver may connect to the server, obtain the updated firmware parameters, and store the updated firmware parameters in the system file. Therefore, the firmware parameters can be updated each time the drive registration is carried out after the start-up. The firmware parameters of the same equipment type can be simultaneously acquired from the server and respectively stored in the corresponding folders.
In another embodiment, after the driver registration is completed, the memory space occupied by the specific firmware parameter may be released. After the drive finishes the firmware, the firmware parameter data is not needed to be used, so that the memory space occupied by the specific firmware parameter can be released, the specific firmware parameter data in the memory can be deleted, or the specific firmware parameter is covered by the data subsequently written into the memory, so that the memory space is released, the practical efficiency of the memory is improved, and the system performance of the user terminal is improved.
The drive registration method of the invention stores the equipment firmware parameters in the system folder, when drive initialization is carried out, after equipment corresponding to the drive is searched, the identification code of the equipment is obtained, then the system folder is scanned, the specific firmware parameters matched with the identification code of the equipment are obtained and stored in the memory, and if firmware upgrading is needed, the firmware parameters are written into the equipment chip to complete drive registration. Only the matched specific firmware parameters need to be stored in the memory, so that the memory space of the user terminal can be effectively saved; and the firmware parameters are stored in the system file, so that the portability of the drive codes can be improved, and errors can be avoided when the firmware is issued.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (6)
1. A method of registration of a drive, comprising:
initializing a driver, searching equipment corresponding to the driver and acquiring an identification code of the equipment, wherein firmware parameters of the equipment are stored in a system file, the firmware parameters are used for burning and upgrading firmware of the equipment, aiming at the same equipment, a plurality of firmware parameters are stored in the system file, different firmware parameters correspond to different identification codes, each firmware parameter is stored in a folder of the system in a file form, and the firmware parameters of different items are stored in the folders of the corresponding items;
scanning a folder storing firmware parameters in a system file according to the acquired identification code, acquiring specific firmware parameters corresponding to the identification code, and copying and storing the specific firmware parameters in a memory array;
comparing the specific firmware parameters in the memory array with the firmware parameters written in the equipment chip, and judging whether the equipment needs firmware upgrading;
if so, writing the specific firmware parameters into a chip of the equipment, and then finishing drive registration;
if not, the drive registration is directly completed.
2. The method for registering a driver according to claim 1, further comprising: and acquiring the updated firmware parameters and storing the updated firmware parameters in a system file.
3. The method for registering a driver according to claim 1, further comprising: and after the drive registration is completed, releasing the memory space occupied by the specific firmware parameters.
4. A user terminal, comprising:
the file storage module is used for storing a system file, the system file comprises firmware parameters of equipment, the firmware parameters are used for burning and upgrading firmware of the equipment, aiming at the same equipment, a plurality of firmware parameters are stored in the system file, different firmware parameters correspond to different identification codes, each firmware parameter is stored in a folder of the system in a file form, and the firmware parameters of different projects are stored in the folders of the corresponding projects;
the initialization module is used for initializing a drive, searching equipment corresponding to the drive in the user terminal and acquiring an identification code of the equipment;
the matching module is connected with the file storage module and used for scanning a folder for storing the firmware parameters in the system file according to the acquired identification code, acquiring the specific firmware parameters corresponding to the identification code and storing the specific firmware parameters in the memory array;
the judging module is connected with the matching module and used for comparing the specific firmware parameters in the memory array with the firmware parameters written in the equipment chip and judging whether the equipment needs firmware upgrading;
and the registration module is connected with the judgment module, and is used for completing drive registration after the specific firmware parameters are written into a chip of the equipment if firmware upgrading is needed, and is used for directly completing drive registration if firmware upgrading is not needed.
5. The user terminal according to claim 4, further comprising: and the updating module is connected with the file storage module and used for acquiring the updated firmware parameters and storing the updated firmware parameters in a system file.
6. The user terminal according to claim 4, further comprising: and the release module is connected with the registration module and used for releasing the memory space occupied by the specific firmware parameters after the drive registration is finished.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710748880.4A CN107423075B (en) | 2017-08-28 | 2017-08-28 | Driven registration method and user terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710748880.4A CN107423075B (en) | 2017-08-28 | 2017-08-28 | Driven registration method and user terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107423075A CN107423075A (en) | 2017-12-01 |
| CN107423075B true CN107423075B (en) | 2021-06-08 |
Family
ID=60434544
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710748880.4A Active CN107423075B (en) | 2017-08-28 | 2017-08-28 | Driven registration method and user terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107423075B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110958602A (en) * | 2019-11-14 | 2020-04-03 | 深圳奇未智能科技有限公司 | Firmware compatibility method and device for Bluetooth equipment |
| CN116795452B (en) * | 2023-07-20 | 2024-04-02 | 龙芯中科(北京)信息技术有限公司 | Method, device and equipment for determining compatibility of driving program |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101702143A (en) * | 2009-12-02 | 2010-05-05 | 深圳华为通信技术有限公司 | Method and device for modifying driving and matching information of USB device |
| CN102063320A (en) * | 2011-01-06 | 2011-05-18 | 华为终端有限公司 | Work mode switching methods, USB (Universal Serial Bus) equipment and host machine equipment |
| CN102609285A (en) * | 2012-02-06 | 2012-07-25 | 中兴通讯股份有限公司 | Method for intelligent drive matched loading |
| CN107077435A (en) * | 2014-09-19 | 2017-08-18 | 株式会社艾拉博 | The register method of the device driver of device driver register device and use the device driver register device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6360362B1 (en) * | 1998-02-20 | 2002-03-19 | Intel Corporation | Automatic update of camera firmware |
| CN103353835B (en) * | 2013-01-17 | 2016-08-10 | 珠海全志科技股份有限公司 | The migration process method and device of the compatible multiple Sensor equipment of the same race of android system Sensor HAL layer |
| US9652260B2 (en) * | 2013-12-04 | 2017-05-16 | International Business Machines Corporation | Scriptable hierarchical emulation engine |
-
2017
- 2017-08-28 CN CN201710748880.4A patent/CN107423075B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101702143A (en) * | 2009-12-02 | 2010-05-05 | 深圳华为通信技术有限公司 | Method and device for modifying driving and matching information of USB device |
| CN102063320A (en) * | 2011-01-06 | 2011-05-18 | 华为终端有限公司 | Work mode switching methods, USB (Universal Serial Bus) equipment and host machine equipment |
| CN102609285A (en) * | 2012-02-06 | 2012-07-25 | 中兴通讯股份有限公司 | Method for intelligent drive matched loading |
| CN107077435A (en) * | 2014-09-19 | 2017-08-18 | 株式会社艾拉博 | The register method of the device driver of device driver register device and use the device driver register device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107423075A (en) | 2017-12-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103412769A (en) | External card parameter configuration method, equipment and system | |
| CN101923473B (en) | Embedded electronic device and method for updating firmware thereof | |
| WO2017202338A1 (en) | Method and system for loading drive to set-top box | |
| CN111444030B (en) | Data storage device and method for avoiding firmware failure | |
| US20100064036A1 (en) | Peripheral device operation method, peripheral device and host | |
| CN104679540A (en) | Computer system and computer system starting method | |
| WO2016078263A1 (en) | Upgrading control device and terminal, terminal upgrading method and system, and storage medium | |
| CN103514015A (en) | Method and device for booting operation system from storage medium | |
| CN110597523A (en) | Board card firmware burning method, device and system, board card and terminal equipment | |
| CN107423075B (en) | Driven registration method and user terminal | |
| CN105824678A (en) | Method and device for installing operating system | |
| CN106569854B (en) | Method and system for setting equipment firmware and realizing factory test | |
| CN104657161A (en) | Method and device for updating firmware of mobile terminal | |
| CN102609290B (en) | The method for upgrading software of electronic product | |
| CN109033816B (en) | Domestic office peripheral drive management method and system on kylin operating system platform | |
| CN106484719B (en) | Method and terminal for expanding mobile phone storage | |
| CN101000580A (en) | NAND flash information extraction method and NAND flash automatic identification method | |
| US8799542B2 (en) | System and method for providing remote device driver | |
| CN102830988A (en) | Firmware updating method and related computer system | |
| CN114816491A (en) | System upgrading method and device for multi-system mobile terminal and terminal | |
| CN109445698B (en) | Method and device for querying multi-chip flash state and computer readable storage medium | |
| CN107436778A (en) | A kind of high reliability upgrade method of unmanned systems | |
| CN106445504A (en) | Update method and system of mobile terminal device driver | |
| CN113360161A (en) | Resource upgrading method and related product | |
| CN101299190B (en) | Software upgrading method, system and built-in equipment of read-only file system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 518057 Shennan Avenue, Yuehai Street, Shenzhen City, Guangdong Province, 9789 Desai Science and Technology Building, 17th Floor (15th Floor of Nature Floor) 1702-1703 Applicant after: Shenzhen acoustic Cmi Holdings Ltd Address before: 518057 Shennan Avenue, Yuehai Street, Shenzhen City, Guangdong Province, 9789 Desai Science and Technology Building, 17th Floor (15th Floor of Nature Floor) 1702-1703 Applicant before: Shenzhen sound Holdings Limited |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |