CN116795452B - Method, device and equipment for determining compatibility of driving program - Google Patents
Method, device and equipment for determining compatibility of driving program Download PDFInfo
- Publication number
- CN116795452B CN116795452B CN202310899861.7A CN202310899861A CN116795452B CN 116795452 B CN116795452 B CN 116795452B CN 202310899861 A CN202310899861 A CN 202310899861A CN 116795452 B CN116795452 B CN 116795452B
- Authority
- CN
- China
- Prior art keywords
- information
- chip
- version
- driver
- version information
- 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
- 238000000034 method Methods 0.000 title claims abstract description 48
- 230000002093 peripheral effect Effects 0.000 claims abstract description 127
- 238000013500 data storage Methods 0.000 claims description 6
- 230000004044 response Effects 0.000 claims description 5
- 230000008569 process Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000008439 repair process Effects 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
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/445—Program loading or initiating
- G06F9/44536—Selecting among different versions
-
- 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/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4494—Execution paradigms, e.g. implementations of programming paradigms data driven
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The method, the device and the equipment for determining the compatibility of the driver provided by the application comprise the following steps: responding to a first initialization instruction aiming at the electronic equipment, and acquiring a version number of a system-in-chip in the electronic equipment; determining version information of the system-on-chip based on the version number; registering the version information into the kernel of the system-in-chip; responding to a second initialization instruction aiming at the peripheral equipment, and matching version information with configuration information in the first structural body based on a driving program of the peripheral equipment to obtain a matching result; the first structure body comprises at least one piece of configuration information; the configuration information is version information of a system-on-chip which cannot be compatible with the peripheral equipment; if the matching result indicates that the configuration information which is the same as the version information exists in the first structural body, the driver of the peripheral equipment is not compatible with the system-in-chip. By the method, the compatibility between the current electronic device and the peripheral device driver can be automatically determined.
Description
Technical Field
The present invention relates to the field of electronics, and in particular, to a method, an apparatus, and a device for determining driver compatibility.
Background
At present, when installing a peripheral device, it is generally required to ensure compatibility between a system-level chip in an electronic device and a driver corresponding to the peripheral device, so as to ensure that the system-level chip can realize accurate control of the peripheral device.
In the related art, it is generally necessary to manually determine compatibility between a peripheral device and a system-in-chip in an electronic device in which the peripheral device is currently installed, and a certain expertise is required for determination.
How to automatically determine the compatibility of the driver of the peripheral device is a problem to be solved.
Disclosure of Invention
The application provides a method, a device and equipment for determining compatibility of a driver, which are used for automatically determining the compatibility between a system-in-chip and a peripheral driver in electronic equipment in the starting process of the electronic equipment.
In a first aspect, the present application provides a method for determining driver compatibility, including:
responding to a first initialization instruction aiming at electronic equipment, and acquiring a version number of a system-on-chip in the electronic equipment; determining version information of the system-on-chip based on the version number; the first initialization instruction is used for indicating to start the electronic equipment;
Registering the version information into a kernel of the system-on-chip;
responding to a second initialization instruction aiming at peripheral equipment, and matching the version information with configuration information in a first structure body based on a driver of the peripheral equipment to obtain a matching result; the peripheral device is connected with the electronic device; the first structure body comprises at least one piece of configuration information; the configuration information is version information of a system-in-chip which cannot be compatible with the peripheral equipment; the second initialization instruction is used for indicating to initially configure the peripheral device;
and if the matching result represents that the configuration information which is the same as the version information exists in the first structural body, determining that the driver of the peripheral equipment is incompatible with the system-in-chip.
In one possible implementation, obtaining the version number of the system on chip in the electronic device includes:
acquiring the position information of a register in equipment tree source code DTS in electronic equipment; the register is used for storing the version number; the location information is used for indicating address information of the register;
and acquiring the version number stored by the register according to the position information.
In one possible implementation manner, the location information includes address information and data format information of a register; the data format information is used for indicating a data storage mode of the register for storing the version number;
according to the position information, obtaining the version number stored in the register comprises the following steps:
according to the address information, acquiring storage data in a register indicated by the address information;
and determining the version number according to the stored data and the data format information.
In one possible implementation, determining version information of the system-on-chip based on the version number includes:
extracting target characters corresponding to the designated bits in the version number;
determining version information corresponding to the character in a second structure according to the target character; the second structure body comprises a plurality of version information, and each version information corresponds to the character information one by one.
In one possible implementation, the configuration information includes a plurality of data to be matched; the data to be matched has a unique identifier;
based on the driver of the peripheral device, matching the version information with the configuration information in the first structure body to obtain a matching result, including:
If the driver program based on the peripheral equipment determines that each piece of data to be matched contained in the configuration information in the first structure body is identical to the data field in the version information, determining that the matching result represents that the configuration information identical to the version information exists in the first structure body; and the data field is a field with the same identification as the data to be matched in the version information.
In one possible implementation manner, the data to be matched is any one of a device identifier of an electronic device carrying a system-level chip, a batch number of the system-level chip, and a version number of the system-level chip.
In one possible implementation, the method further includes:
if the matching result represents that the configuration information which is the same as the version information does not exist in the first structural body, determining that the driver of the peripheral equipment is compatible with the system-in-chip;
and initializing and configuring the peripheral equipment based on the driving program of the peripheral equipment.
In a second aspect, the present application provides a device for determining driver compatibility, including:
an obtaining unit, configured to obtain a version number of a system-in-chip in an electronic device in response to a first initialization instruction for the electronic device; the first initialization instruction is used for indicating to start the electronic equipment;
A first determining unit configured to determine version information of the system-in-chip based on the version number;
a registration unit, configured to register the version information into a kernel of the system-in-chip;
a matching unit, configured to respond to a second initialization instruction for a peripheral device, and match the version information with configuration information in the first structure body based on a driver of the peripheral device, so as to obtain a matching result; the peripheral device is connected with the electronic device; the first structure body comprises at least one piece of configuration information; the configuration information is version information of a system-in-chip which cannot be compatible with the peripheral equipment; the second initialization instruction is used for indicating to initially configure the peripheral device;
and the second determining unit is used for determining that the driver of the peripheral equipment is incompatible with the system-on-chip if the matching result indicates that the configuration information which is the same as the version information exists in the first structural body.
In one possible implementation, the obtaining unit includes:
the first acquisition module is used for responding to a first initialization instruction aiming at the electronic equipment and acquiring the position information of the register in equipment tree source codes DTS in the electronic equipment; the register is used for storing the version number; the location information is used for indicating address information of the register;
And the second acquisition module is used for acquiring the version number stored by the register according to the position information.
In one possible implementation manner, the location information includes address information and data format information of a register; the data format information is used for indicating a data storage mode of the register for storing the version number;
the second acquisition module is specifically configured to:
according to the address information, acquiring storage data in a register indicated by the address information;
and determining the version number according to the stored data and the data format information.
In one possible implementation manner, the first determining unit includes:
the extraction module is used for extracting target characters corresponding to the designated bits in the version number;
the determining module is used for determining version information corresponding to the target character in the second structural body according to the target character; the second structure body comprises a plurality of version information, and each version information corresponds to the character information one by one.
In one possible implementation, the configuration information includes a plurality of data to be matched; the data to be matched has a unique identifier;
the matching unit is specifically used for:
If the driver program based on the peripheral equipment determines that each piece of data to be matched contained in the configuration information in the first structure body is identical to the data field in the version information, determining that the matching result represents that the configuration information identical to the version information exists in the first structure body; and the data field is a field with the same identification as the data to be matched in the version information.
In one possible implementation manner, the data to be matched is any one of a device identifier of an electronic device carrying a system-level chip, a batch number of the system-level chip, and a version number of the system-level chip.
In one possible implementation, the apparatus further includes:
a third determining unit, configured to determine that a driver of the peripheral device is compatible with the system-on-chip if the matching result characterizes that the configuration information identical to the version information does not exist in the first structure body;
and the configuration unit is used for initializing and configuring the peripheral equipment based on the driving program of the peripheral equipment.
In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively coupled to the processor; the memory stores computer-executable instructions; the processor executes computer-executable instructions stored in the memory to implement the method of any one of the first aspects.
In a fourth aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions for performing the method of any of the first aspects when executed by a processor.
In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the method of any one of the first aspects.
The method, device and equipment for determining the compatibility of the driver provided by the application comprise the following steps: responding to a first initialization instruction aiming at electronic equipment, and acquiring a version number of a system-on-chip in the electronic equipment; determining version information of the system-on-chip based on the version number; registering the version information into a kernel of the system-on-chip; responding to a second initialization instruction aiming at peripheral equipment, and matching the version information with configuration information in a first structure body based on a driver of the peripheral equipment to obtain a matching result; the peripheral device is connected with the electronic device; the first structure body comprises at least one piece of configuration information; the configuration information is version information of a system-in-chip which cannot be compatible with the peripheral equipment; and if the matching result represents that the configuration information which is the same as the version information exists in the first structural body, determining that the driver of the peripheral equipment is incompatible with the system-in-chip. Furthermore, by the method, before the configuration of the peripheral device driver, the version information of the configured system-level chip can be actively registered in the kernel when the electronic device is started, and when the driver is required to be installed, the electronic device can compare with the first structure body which cannot be compatible with the peripheral device driver based on the version information registered in advance, so that the compatibility between the current electronic device and the peripheral device driver can be automatically determined.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
Fig. 1 is a flow chart of a method for determining driver compatibility according to an embodiment of the present application;
FIG. 2 is a flowchart illustrating another method for determining driver compatibility according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of a device for determining driver compatibility according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of another device for determining driver compatibility according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Specific embodiments thereof have been shown by way of example in the drawings and will herein be described in more detail. These drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with aspects of the present application.
Currently, a general-purpose driver for a peripheral device can be adapted to a plurality of different types of system-on-chips, but for some types of system-on-chips, inapplicability still occurs. Therefore, when the system-on-chip needs to connect a peripheral through a peripheral controller internally integrated with the system-on-chip, or the system-on-chip needs to connect a peripheral through a peripheral controller connected with the system-on-chip, compatibility between the system-on-chip and a driver corresponding to the current peripheral is generally considered. The driver of the peripheral device can convert the control instruction which is required to be sent to the peripheral device by the system-level chip, so that the peripheral device can accurately identify the instruction sent by the system-level chip. In addition, the driver of the peripheral device can also convert the instruction fed back by the peripheral device, so that the system-in-chip can accurately identify the instruction of the peripheral device. When the driver of the peripheral device is not compatible with the system-level chip, at this time, accurate communication between the system-level chip and the peripheral device cannot be realized, and thus the peripheral device cannot work normally.
Therefore, when the peripheral device is installed, if the compatibility between the driver of the peripheral device and the system-in-chip can be automatically identified, the phenomenon that the follow-up peripheral device and the system-in-chip cannot be accurately controlled can be avoided.
In the application, a section of driver program which can be used for acquiring the version information of a system-level chip in the electronic equipment is added in an initializing program started by the electronic equipment, and the version information of the system-level chip is determined. When the peripheral device is installed and configured by the electronic device, the driver of the peripheral device can automatically determine whether the driver of the current peripheral device is matched and compatible with the system-level chip based on the determined version information of the system-level chip, so that the problem that the compatibility determination cannot be automatically performed in the related art is avoided.
The following describes the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 1 is a flow chart of a method for determining driver compatibility according to an embodiment of the present application, as shown in fig. 1, where the method includes:
s101, responding to a first initialization instruction aiming at the electronic equipment, and acquiring a version number of a system-in-chip in the electronic equipment, wherein the first initialization instruction is used for indicating to start the electronic equipment.
The present embodiment is described with a system-on-chip as an execution body. In order to automatically determine the compatibility between a System on Chip (SoC) in an electronic device and a driver of a peripheral device to be installed, version information of the corresponding System on Chip in the electronic device needs to be searched and acquired first.
Specifically, the method for searching and obtaining the version information of the system-on-chip in the electronic device may be a written section of program code in practical application, and the section of code may be set in an initialization start program corresponding to the system-on-chip. When the system-level chip receives a first initialization instruction for indicating the electronic device to start, the version number corresponding to the system-level chip in the electronic device is acquired first.
In one example, when the version number corresponding to the system-in-chip is obtained, the version number may be obtained by performing communication interaction with other external devices except the electronic device; for example, the rest of external devices can be used for managing version numbers corresponding to system-level chips corresponding to the plurality of electronic devices. The electronic device may directly request the external device to obtain the version number corresponding to the system-in-chip configured by the electronic device.
S102, based on the version number, version information of the system-in-chip is determined.
In this embodiment, after the system-level chip obtains the version number corresponding to the configured system-level chip, further, version information corresponding to the system-level chip may be obtained according to the version number of the system-level chip. The version information of the system-level chip may be specifically used to describe the configuration content corresponding to the system-level chip. It can be understood that version information corresponding to the system level chip corresponding to the different version numbers is different.
In one example, when version information corresponding to a system-in-chip is acquired, in order to avoid a problem that a storage space in an electronic device occupies a large amount, the version information may be stored in a common storage device, so that the electronic device may determine, by using the storage device, the version information corresponding to the version number by feeding back the version number corresponding to the electronic device to the common storage device.
S103, registering the version information into the kernel of the system-in-chip.
In this embodiment, after the system-level chip obtains the version information corresponding to the system-level chip, the version information may be registered in the kernel in the system-level chip, so that when the subsequent system-level chip initializes the driver of the peripheral device, the version information of the system-level chip configured by the electronic device may be directly obtained from the kernel. Specifically, in practical application, the registration of the version information can be completed by calling the soc_device_register function.
S104, responding to a second initialization instruction aiming at the peripheral equipment, and matching version information with configuration information in the first structural body based on a driving program of the peripheral equipment to obtain a matching result; the peripheral equipment is connected with the electronic equipment; the first structure body comprises at least one piece of configuration information; the configuration information is version information of a system-in-chip which cannot be compatible with the peripheral device, and the second initialization instruction is used for indicating initializing configuration of the peripheral device.
In the electronic device starting process, when a second initialization instruction for installing and configuring a driver of a peripheral device associated with the electronic device is detected, at this time, the system-level chip may acquire version information of the system-level chip of the electronic device corresponding to the current system-level chip from a kernel of the system-level chip when the driver corresponding to the peripheral device is initialized and operated. And before the configuration driver is installed, firstly, matching the acquired version information with the configuration information in the first structural body based on a comparison program pre-configured by the driver of the peripheral equipment, and further determining a matching result between the version information and the first structural body.
The first structure body is preset for the electronic equipment and is used for including data information of a plurality of configuration information. The configuration information in the first structural body is version information of an incompatible system-level chip corresponding to a driver of a peripheral device associated with the current electronic device.
Before the configuration driver is actually installed, firstly comparing version information of a system-level chip corresponding to the current electronic equipment with incompatible configuration information corresponding to peripheral equipment to be installed of the electronic equipment, and further determining whether the current version information is located in the first structural body. In the actual application process, when the comparison is performed, the matching between the first structural body and the currently acquired SoC version information can be realized by calling a soc_device_match function.
S105, if the matching result represents that the configuration information which is the same as the version information exists in the first structural body, determining that the driver of the peripheral equipment is incompatible with the system-in-chip.
By way of example, through the above-described matching process, when it is determined that the version information and the configuration information in the first structure are the same, at this time, it is characterized that the driver corresponding to the current peripheral device cannot be compatible with the system-on-chip.
It can be understood that in this embodiment, version information corresponding to a system-level chip corresponding to the electronic device is actively obtained during the starting process of the electronic device, so that the version information of the system-level chip corresponding to the current electronic device and the first structure body composed of configuration information which cannot be compatible with the peripheral device can be compared later before the driver corresponding to the peripheral device is installed, so as to determine compatibility between the driver of the current peripheral device and the system-level chip, and facilitate a user to adjust and modify the driver in time under the condition that the driver cannot be compatible with the driver.
Fig. 2 is a flow chart of another method for determining driver compatibility according to an embodiment of the present application, as shown in fig. 2, where the method includes:
s201, responding to a first initialization instruction aiming at the electronic equipment, and acquiring the position information of a register in equipment tree source code DTS in the electronic equipment; the register is used for storing the version number; the location information is used for indicating address information of the register; the first initialization instruction is used for indicating to start the electronic device.
The execution body in the present embodiment is exemplarily described by taking a system-on-chip as an example. In this embodiment, after the electronic device receives the first initialization instruction for instructing the electronic device to start, the electronic device first obtains the version number of the system-in-chip corresponding to the electronic device.
Specifically, in this embodiment, in order to obtain the corresponding version number, an address of a register in the electronic device for storing the version number corresponding to the system-in-chip is predefined in a device tree source code (Device Tree Source, DTS for short) corresponding to the electronic device. The DTS is a description file in the electronic device, which is used for describing a device included in the electronic device. When the system-on-chip needs to acquire the version number, first, location information of a register for storing the version number may be acquired based on a DTS file in the electronic device.
S202, according to the position information, the version number stored in the register is obtained.
For example, after the electronic device acquires the above-described location information, the version number stored in the register may be acquired directly based on the address information of the register indicated by the location information.
It can be appreciated that in this embodiment, the location information of the register for storing the SoC version number is predefined in the DTS file, so that the electronic device can timely obtain the corresponding SoC version number based on the location information, thereby improving the compatibility judgment efficiency.
In one example, the location information includes address information and data format information of a register; the data format information is used to indicate the data storage mode of the register storage version number, and step S202 may be specifically implemented by the following steps: acquiring storage data in a register indicated by the address information according to the address information; and determining the version number according to the stored data and the data format information. "
In this embodiment, when the location information of the register for storing the SoC version number is set in the DTS file, specifically, address information corresponding to the register may be included in the location information, and in addition, data format information corresponding to the register may be additionally set. The data format information may be understood as a data storage mode corresponding to the register when storing the SoC version number. In order to ensure that the SoC identification can be accurately acquired by the electronic device, the electronic device acquires the stored data stored in the register based on the address information. Then, the electronic device can obtain an accurate version number according to the acquired data format information and the acquired storage data.
For example, the data format information of the register may be specifically any one of the large-end mode or the small-end mode. The big-end mode is understood to be a mode in which high-order bytes are stored in a low-order address of a register, and low-order bytes are stored in a high-order address of a register. The small end mode may understand that the bits store the low order bytes at the low address of the register and the high order bytes at the high address. When the electronic device acquires the stored data in the register, the stored data can be ordered from high byte to low byte according to the corresponding mode, so that the SoC version number can be accurately acquired.
It can be appreciated that in this embodiment, the accuracy of the obtained version number may be further ensured by setting the address information and the data format information of the register for storing the SoC version number in the DTS, respectively.
S203, extracting target characters corresponding to the specified positions in the version numbers.
In this embodiment, when the electronic device determines version information corresponding to the system-in-chip according to the version number, at this time, version information corresponding to the version number may be determined according to a second structure set in the electronic device. Wherein, the second structure body is provided with a plurality of version information, and also has character information corresponding to each version information one by one. The character information corresponding to each version information is obtained according to the appointed character in the version number corresponding to the version information.
Further, when version information of the SoC in the electronic device is determined according to the version number, first, the character of the specified bit in the obtained SoC version number of the current electronic device may be extracted as the target character.
S204, determining version information corresponding to the target character in the second structural body according to the target character; the first structure body comprises a plurality of version information, and each version information corresponds to the character information one by one.
For example, after the electronic device extracts the target character, the target character may be compared with the character information corresponding to each version information in the second structure body, and the version information corresponding to the character information identical to the target character may be used as the SoC version information of the currently acquired electronic device.
It can be appreciated that in this embodiment, when the second structure is stored in the electronic device, the version information does not need to be in one-to-one correspondence with the complete version number, but only corresponds to the character information extracted from the version number, so that the space occupation amount of the second structure can be reduced, and in the subsequent comparison process with the target character, the characters to be compared can be reduced, so as to improve the comparison efficiency.
S205, registering the version information into the kernel of the system-in-chip.
For example, the specific principle of step S205 may be referred to step S103, which is not described herein.
S206, responding to a second initialization instruction aiming at the peripheral equipment, and matching version information with configuration information in the first structural body based on a driving program of the peripheral equipment to obtain a matching result; the peripheral equipment is connected with the electronic equipment; the first structure body comprises at least one piece of configuration information; the configuration information is version information of a system-in-chip which cannot be compatible with the peripheral device, and the second initialization instruction is used for indicating initializing configuration of the peripheral device.
In one example, when the step "match version information and configuration information in the first structure to obtain a matching result based on the driver of the peripheral device" in step S206 is performed, this may be achieved by: if the driver program based on the peripheral equipment determines that each piece of data to be matched contained in the configuration information in the first structural body is identical to the data field in the version information, determining that the configuration information identical to the version information exists in the first structural body by the matching result; the data field is a field with the same identification as the data to be matched in the version information; the configuration information comprises a plurality of data to be matched; the data to be matched has a unique identification.
In this embodiment, when the SoC version information of the current electronic device actually acquired is compared with the first structure based on the driver of the peripheral device before the driver corresponding to the peripheral device is configured, each piece of data to be matched included in the SoC version information and the configuration information in the first structure needs to be compared.
Specifically, the configuration information included in the first structure body is generally composed of a plurality of data to be matched, where each data to be matched corresponds to an identifier. That is, the configuration information is composed of data to be matched corresponding to each of the plurality of identifiers. For example, in practical application, the SoC version information corresponds to a lot of data, in order to reduce a complex phenomenon of comparison between the configuration information in the subsequent first structure body and the version information actually obtained, when the configuration information is set, all original version information is not required to be used as the configuration information, but a plurality of data are extracted from the version information corresponding to the configuration information to be used as data to be matched, which can represent the version information.
When actually comparing the SoC version information with the configuration information in the first structure, only whether the data to be matched in the configuration information is included in the actually acquired SoC version information needs to be compared. When a plurality of pieces of data to be matched contained in one piece of configuration information exist in the first structural body and are all located in the SoC version information which is actually acquired, namely, the data to be matched corresponding to the same field identification is identical to the data field in the SoC version information, at the moment, the fact that the configuration information identical to the version information exists in the first structural body is determined. Further, a mismatch between SoC version information of the current electronic device and drivers of the peripheral device is determined.
It can be understood that the configuration information in this embodiment may be composed of a plurality of data to be matched, and further, the plurality of data to be matched characterizes SoC version information incompatible with a driver, and when the plurality of data to be matched in the configuration information are all located in the actually obtained SoC version information of the electronic device, incompatibility between the driver of the peripheral device to be installed and the SoC can be further determined. When the configuration information of the first structure is composed of a plurality of data to be matched, but not all version information, when the SoC version information carried by the configuration information is registered in the kernel, only the data corresponding to the specified identifier in the currently acquired SoC version information may be registered as the SoC version information, and further, the occupation of the memory space in the kernel may be reduced.
In one example, the data to be matched is any one of a device identification of an electronic device on which the system-on-chip is mounted, a lot number of the system-on-chip, and a system-on-chip version number.
For example, in practical application, the data to be matched may select the device identifier of the electronic device included in the version information, that is, the device identifier of the electronic device on which the SoC is mounted, or may be a lot number corresponding to the SoC (where one lot number may correspond to multiple version numbers), or may also include the version number of the SoC. It should be noted that, the data to be matched herein is only an example, and in practical application, the rest of identification information in the SoC version information, which can be used for distinguishing different SoC versions, can be used as the data to be matched.
S207, if the matching result represents that the configuration information which is the same as the version information exists in the first structural body, determining that the driver of the peripheral device is incompatible with the system-in-chip.
For example, the technical principle of step S207 may be referred to step S105, which is not described herein.
In one possible implementation, when it is determined that the driver is incompatible with the SoC, the system-on-chip may automatically obtain a preconfigured driver repair file, and repair the driver of the peripheral device to be installed, so as to ensure compatibility between the driver of the peripheral device and the system-on-chip. It should be noted that, the driver repair file herein is a solution suitable for solving the incompatibility between the driver of the peripheral device set in the current electronic device and the current SoC. Or if the driver repair file cannot be obtained, the alarm prompt message can be directly sent out, so that a user can repair the driver timely.
In one possible implementation, when the matching result indicates that the configuration information which is the same as the version information does not exist in the first structural body, determining that the driver of the peripheral device is compatible with the system-in-chip; the configuration of the peripheral device is initialized based on the driver of the peripheral device.
In this embodiment, when the system-on-chip compares the first structure body with the currently acquired SoC version information, it is determined that the driver of the peripheral device currently required to be installed is compatible with the SoC, and then the subsequent initialization configuration operation of the peripheral device can be performed, so that accurate communication between the subsequent peripheral device and the system-on-chip can be performed.
It can be appreciated that in the compatibility determining method provided in this embodiment, the location information of the register for storing the SoC version number is predefined in the DTS file, so that the corresponding SoC version number can be timely obtained based on the location information, thereby improving the compatibility judging efficiency. Furthermore, the address information and the data format information of the register for storing the SoC version number can be further set in the DTS, so that the accuracy of the acquired version number is ensured. In addition, when version information is determined based on the second storage structure, the version information in the second structure body stored by the electronic device does not need to be in one-to-one correspondence with the complete version number, but only corresponds to character information extracted from the version number, so that the space occupation amount of the second structure body can be reduced, and in the subsequent comparison process with target characters, characters needing to be compared can be reduced, so that the comparison efficiency is improved.
Fig. 3 is a schematic structural diagram of a device for determining compatibility of a driver, which is provided in an embodiment of the present application, and as shown in fig. 3, the device is applied to a system-on-chip, and the determining device includes:
the obtaining unit 301 is configured to obtain a version number of a system-on-chip in the electronic device in response to a first initialization instruction for the electronic device, where the first initialization instruction is used to instruct to start the electronic device.
A first determining unit 302, configured to determine version information of the system on chip based on the version number.
A registration unit 303, configured to register the version information into a kernel of the system-on-chip.
A matching unit 304, configured to match version information and configuration information in the first structure body based on a driver of the peripheral device in response to a second initialization instruction for the peripheral device, to obtain a matching result; the peripheral equipment is connected with the electronic equipment; the first structure body comprises at least one piece of configuration information; the configuration information is version information of a system-on-chip which cannot be compatible with the peripheral equipment; the second initialization instruction is used for indicating the initialization configuration peripheral device.
The second determining unit 305 is configured to determine that the driver of the peripheral device is incompatible with the system-on-chip if the matching result indicates that the configuration information identical to the version information exists in the first structure.
The device provided in this embodiment is configured to implement the technical scheme provided by the method, and the implementation principle and the technical effect are similar and are not repeated.
Fig. 4 is a schematic structural diagram of another device for determining driver compatibility according to an embodiment of the present application, where, based on the device structure shown in fig. 3, the obtaining unit 301 includes:
a first obtaining module 3011, configured to obtain location information of a register in a device tree source code DTS in an electronic device in response to a first initialization instruction for the electronic device; the register is used for storing the version number; the location information is used to indicate address information of the register.
And the second obtaining module 3012 is configured to obtain the version number stored in the register according to the location information.
In one possible implementation, the location information includes address information and data format information of the register; the data format information is used for indicating a data storage mode of the register for storing the version number.
The second obtaining module 3012 is specifically configured to: according to the address information, acquiring storage data in a register indicated by the address information; and determining the version number according to the stored data and the data format information.
In one possible implementation, the first determining unit 302 includes:
the extracting module 3021 is configured to extract the target character corresponding to the specified position in the version number.
A determining module 3022, configured to determine, in the second structure, version information corresponding to the character according to the target character; the second structure body comprises a plurality of version information, and each version information corresponds to the character information one by one.
In one possible implementation, the configuration information includes a plurality of data to be matched; the data to be matched has a unique identifier;
the matching unit 304 is specifically configured to:
if the driver program based on the peripheral equipment determines that each piece of data to be matched contained in the configuration information in the first structural body is identical to the data field in the version information, determining that the configuration information identical to the version information exists in the first structural body by the matching result; the data field is a field with the same identification as the data to be matched in the version information.
In one possible implementation, the data to be matched is any one of a device identification of an electronic device on which the system-on-chip is mounted, a lot number of the system-on-chip, and a version number of the system-on-chip.
In one possible implementation, the apparatus further includes:
The third determining unit 306 is configured to determine that the driver of the peripheral device is compatible with the system-on-chip if the matching result indicates that the configuration information identical to the version information does not exist in the first structure body.
A configuration unit 307 for initializing the configuration of the peripheral device based on the driver of the peripheral device.
The device provided in this embodiment is configured to implement the technical scheme provided by the method, and the implementation principle and the technical effect are similar and are not repeated.
The application provides an electronic device, comprising: a memory, a processor;
a memory storing processor-executable instructions;
and a processor for executing the method provided in the above embodiment according to the executable instructions.
Fig. 5 is a schematic structural diagram of an electronic device provided in an embodiment of the present application, as shown in fig. 5, where the electronic device includes:
a processor 291, the electronic device further comprising a memory 292; a communication interface (Communication Interface) 293 and bus 294 may also be included. The processor 291, the memory 292, and the communication interface 293 may communicate with each other via the bus 294. Communication interface 293 may be used for information transfer. The processor 291 may call logic instructions in the memory 292 to perform the methods of the above-described embodiments.
Further, the logic instructions in memory 292 described above may be implemented in the form of software functional units and stored in a computer-readable storage medium when sold or used as a stand-alone product.
The memory 292 is a computer readable storage medium, and may be used to store a software program, a computer executable program, and program instructions/modules corresponding to the methods in the embodiments of the present application. The processor 291 executes functional applications and data processing by running software programs, instructions and modules stored in the memory 292, i.e., implements the methods of the method embodiments described above.
Memory 292 may include a storage program area that may store an operating system, at least one application program required for functionality, and a storage data area; the storage data area may store data created according to the use of the terminal device, etc. Further, memory 292 may include high-speed random access memory, and may also include non-volatile memory.
The present application provides a computer-readable storage medium having stored therein computer-executable instructions that, when executed by a processor, perform the method of any one of the above.
The present application provides a computer program product comprising a computer program which, when executed by a processor, implements the method of any one of the claims.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (10)
1. A method for determining driver compatibility, comprising:
responding to a first initialization instruction aiming at electronic equipment, and acquiring a version number of a system-on-chip in the electronic equipment; determining version information of the system-on-chip based on the version number; the first initialization instruction is used for indicating to start the electronic equipment;
Registering the version information into a kernel of the system-on-chip;
responding to a second initialization instruction aiming at peripheral equipment, and matching the version information with configuration information in a first structure body based on a driver of the peripheral equipment to obtain a matching result; the peripheral device is connected with the electronic device; the first structure body comprises at least one piece of configuration information; the configuration information is version information of a system-in-chip which cannot be compatible with the peripheral equipment; the second initialization instruction is used for indicating to initially configure the peripheral device;
and if the matching result represents that the configuration information which is the same as the version information exists in the first structural body, determining that the driver of the peripheral equipment is incompatible with the system-in-chip.
2. The method of claim 1, wherein obtaining a version number of a system-on-chip in the electronic device comprises:
acquiring the position information of a register in equipment tree source code DTS in electronic equipment; the register is used for storing the version number; the location information is used for indicating address information of the register;
And acquiring the version number stored by the register according to the position information.
3. The method according to claim 2, wherein the location information includes address information and data format information of a register; the data format information is used for indicating a data storage mode of the register for storing the version number;
according to the position information, obtaining the version number stored in the register comprises the following steps:
according to the address information, acquiring storage data in a register indicated by the address information;
and determining the version number according to the stored data and the data format information.
4. The method of claim 1, wherein determining version information for the system-on-chip based on the version number comprises:
extracting target characters corresponding to the designated bits in the version number;
determining version information corresponding to the character in a second structure according to the target character; the second structure body comprises a plurality of version information, and each version information corresponds to the character information one by one.
5. The method of claim 1, wherein the configuration information includes a plurality of data to be matched; the data to be matched has a unique identifier;
Based on the driver of the peripheral device, matching the version information with the configuration information in the first structure body to obtain a matching result, including:
if the driver program based on the peripheral equipment determines that each piece of data to be matched contained in the configuration information in the first structure body is identical to the data field in the version information, determining that the matching result represents that the configuration information identical to the version information exists in the first structure body; and the data field is a field with the same identification as the data to be matched in the version information.
6. The method of claim 5, wherein the data to be matched is any one of a device identification of an electronic device on which the system-on-chip is mounted, a lot number of the system-on-chip, and a system-on-chip version number.
7. The method according to any one of claims 1-6, further comprising:
if the matching result represents that the configuration information which is the same as the version information does not exist in the first structural body, determining that the driver of the peripheral equipment is compatible with the system-in-chip;
and initializing and configuring the peripheral equipment based on the driving program of the peripheral equipment.
8. A driver compatibility determination apparatus, comprising:
an obtaining unit, configured to obtain a version number of a system-in-chip in an electronic device in response to a first initialization instruction for the electronic device; the first initialization instruction is used for indicating to start the electronic equipment;
a first determining unit configured to determine version information of the system-in-chip based on the version number;
a registration unit, configured to register the version information into a kernel of the system-in-chip;
a matching unit, configured to respond to a second initialization instruction for a peripheral device, and match the version information with configuration information in the first structure body based on a driver of the peripheral device, so as to obtain a matching result; the peripheral device is connected with the electronic device; the first structure body comprises at least one piece of configuration information; the configuration information is version information of a system-in-chip which cannot be compatible with the peripheral equipment; the second initialization instruction is used for indicating to initially configure the peripheral device;
and the second determining unit is used for determining that the driver of the peripheral equipment is incompatible with the system-on-chip if the matching result indicates that the configuration information which is the same as the version information exists in the first structural body.
9. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 1-7.
10. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are for implementing the method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310899861.7A CN116795452B (en) | 2023-07-20 | 2023-07-20 | Method, device and equipment for determining compatibility of driving program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310899861.7A CN116795452B (en) | 2023-07-20 | 2023-07-20 | Method, device and equipment for determining compatibility of driving program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116795452A CN116795452A (en) | 2023-09-22 |
| CN116795452B true CN116795452B (en) | 2024-04-02 |
Family
ID=88043738
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310899861.7A Active CN116795452B (en) | 2023-07-20 | 2023-07-20 | Method, device and equipment for determining compatibility of driving program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116795452B (en) |
Citations (43)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102890587A (en) * | 2012-10-24 | 2013-01-23 | 中山佳时光电科技有限公司 | Driver-free electronic whiteboard control device crossing operating system platforms |
| CN103530121A (en) * | 2013-10-15 | 2014-01-22 | 武汉邮电科学研究院 | Method of compatibility of multiple hardware platforms by RRU single software version |
| CN104268086A (en) * | 2014-09-05 | 2015-01-07 | 南车株洲电力机车研究所有限公司 | Chip identification method and chip compatibility method |
| CN104881604A (en) * | 2014-02-27 | 2015-09-02 | 中兴通讯股份有限公司 | Method and apparatus for operating versions files |
| CN104966022A (en) * | 2015-06-12 | 2015-10-07 | 浪潮电子信息产业股份有限公司 | Chain-of-trust construction method and device based on chip |
| CN104991872A (en) * | 2015-06-19 | 2015-10-21 | 上海卓易科技股份有限公司 | Method and apparatus for implementing driving of intelligent device on peripheral device |
| CN106227516A (en) * | 2016-07-13 | 2016-12-14 | 北京安控科技股份有限公司 | A kind of apparatus and method of network chip adaptive communications |
| CN106293824A (en) * | 2016-08-04 | 2017-01-04 | 青岛海信电器股份有限公司 | A kind of from the method and device processing chip upgrade |
| EP3118703A1 (en) * | 2015-07-13 | 2017-01-18 | Volvo Car Corporation | Safety stoppage device and method for safety stoppage of an autonomous vehicle |
| CN106648758A (en) * | 2016-11-30 | 2017-05-10 | 中国电子科技集团公司第五十八研究所 | Multi-core processor BOOT starting system and method |
| CN107015807A (en) * | 2017-04-06 | 2017-08-04 | 青岛海信宽带多媒体技术有限公司 | A kind of device drives management method |
| CN107423075A (en) * | 2017-08-28 | 2017-12-01 | 深圳传音控股有限公司 | The register method and user terminal of driving |
| CN108055212A (en) * | 2017-12-05 | 2018-05-18 | 锐捷网络股份有限公司 | A kind of method and device of compatible PSE chips |
| CN108268414A (en) * | 2018-03-26 | 2018-07-10 | 福州大学 | SD card driver and its control method based on SPI mode |
| CN108519932A (en) * | 2018-01-24 | 2018-09-11 | 中国电子信息产业集团有限公司第六研究所 | A kind of more performance testing tools based on homemade chip platform |
| CN108631554A (en) * | 2018-03-28 | 2018-10-09 | 成都启臣微电子股份有限公司 | A kind of circuit of automatic adjusument output driving ability |
| CN108984031A (en) * | 2018-07-11 | 2018-12-11 | 深圳贝特莱电子科技股份有限公司 | A kind of method that touch chip supports a variety of touch screens |
| EP3411836A1 (en) * | 2016-02-03 | 2018-12-12 | OPERR Technologies, Inc. | Method and system for on-demand customized services |
| CN109191630A (en) * | 2018-08-04 | 2019-01-11 | 南京理工大学 | A kind of Intelligent door lock in hotel of NFC compatible bluetooth |
| CN109240751A (en) * | 2018-09-04 | 2019-01-18 | 广东小天才科技有限公司 | The outer boxing group compatibility method and electronic equipment of a kind of electronic equipment |
| CN109471661A (en) * | 2018-09-30 | 2019-03-15 | 西安霍威航空科技有限公司 | A kind of embedded board and driving automatic generation method |
| CN109614165A (en) * | 2018-12-04 | 2019-04-12 | 山东财经大学 | A kind of parallel operation method of the multi version of com component and device |
| CN109725575A (en) * | 2018-12-27 | 2019-05-07 | 南京熊猫电子股份有限公司 | The application system of compatible adaptive various field industrial bus communication |
| CN109726279A (en) * | 2018-12-30 | 2019-05-07 | 联想(北京)有限公司 | A kind of data processing method and device |
| CN109981010A (en) * | 2017-12-28 | 2019-07-05 | 沈阳新松机器人自动化股份有限公司 | A kind of motor driven systems and method |
| CN110007857A (en) * | 2019-03-08 | 2019-07-12 | 北京星网锐捷网络技术有限公司 | A kind of life-span prediction method and device of flash chip |
| CN110322842A (en) * | 2019-05-21 | 2019-10-11 | 合肥维信诺科技有限公司 | A kind of pixel-driving circuit and display device |
| CN110405759A (en) * | 2019-07-16 | 2019-11-05 | 大唐微电子技术有限公司 | A kind of chip control system |
| CN110413501A (en) * | 2018-04-26 | 2019-11-05 | 腾讯科技（深圳）有限公司 | Browser compatibility test method, device, system and readable storage medium storing program for executing |
| CN110716874A (en) * | 2019-09-25 | 2020-01-21 | 北京计算机技术及应用研究所 | Method for testing hardware compatibility of domestic operating system |
| CN110750405A (en) * | 2019-10-28 | 2020-02-04 | 天津津航计算技术研究所 | Software compatibility method based on hardware board card identification |
| CN110806891A (en) * | 2019-09-27 | 2020-02-18 | 武汉船舶通信研究所（中国船舶重工集团公司第七二二研究所） | Method and device for generating software version of embedded equipment |
| CN111061643A (en) * | 2019-12-24 | 2020-04-24 | 五八同城信息技术有限公司 | SDK cluster compatibility detection method and device, electronic equipment and storage medium |
| CN111427619A (en) * | 2020-03-26 | 2020-07-17 | 深圳市镭神智能系统有限公司 | Driver self-adaption method, device, updating method, equipment and system |
| EP3716058A1 (en) * | 2019-03-28 | 2020-09-30 | Siemens Aktiengesellschaft | Method for operating a device with a new program code |
| CN111797402A (en) * | 2020-06-17 | 2020-10-20 | 北京世纪互联宽带数据中心有限公司 | Method, device and storage medium for detecting software vulnerability |
| CN112579181A (en) * | 2020-11-13 | 2021-03-30 | 麒麟软件有限公司 | Multi-GPU (graphics processing Unit) drive compatibility method in operating system |
| CN112835623A (en) * | 2021-01-21 | 2021-05-25 | 成都万创科技股份有限公司 | Device compatible device and method based on EEPROM |
| CN113961253A (en) * | 2021-09-29 | 2022-01-21 | 阿里巴巴（中国）有限公司 | Driver calling method and device, electronic equipment and storage medium |
| CN114237727A (en) * | 2021-12-21 | 2022-03-25 | 深圳市有方科技股份有限公司 | Drive loading method and device, computer equipment and storage medium |
| CN114253740A (en) * | 2021-07-12 | 2022-03-29 | 北京鲸鲮信息系统技术有限公司 | Protocol stack data transmission method and device based on Linux kernel |
| CN114510279A (en) * | 2022-01-28 | 2022-05-17 | 浙江大豪明德智控设备有限公司 | Device management method, device, electronic device, storage medium, and program product |
| CN116048640A (en) * | 2022-12-30 | 2023-05-02 | 深圳市创智成科技股份有限公司 | Method for driving IIC equipment in computer system to work normally |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8930901B2 (en) * | 2011-08-15 | 2015-01-06 | International Business Machines Corporation | Automatic selection of lowest configuration feature level by functionality exploited |
| WO2014035463A1 (en) * | 2012-08-31 | 2014-03-06 | Oregon State Board Of Higher Education On Behalf Of Portland State University | System and methods for generating and managing a virtual device |
| US20140333538A1 (en) * | 2013-05-11 | 2014-11-13 | Dexin Corporation | Input device and configuration setting system thereof |
| US10366460B2 (en) * | 2016-03-01 | 2019-07-30 | International Business Machines Corporation | Optimized route sharing |
| US9898354B2 (en) * | 2016-03-21 | 2018-02-20 | Microsoft Technology Licensing, Llc | Operating system layering |
| TWI591486B (en) * | 2016-06-01 | 2017-07-11 | 瑞昱半導體股份有限公司 | Solid state drive control device and method |
| US10076967B2 (en) * | 2016-10-17 | 2018-09-18 | Ford Global Technologies, Llc | Method and apparatus for wireless charging access point identification |
| US11340881B2 (en) * | 2020-04-02 | 2022-05-24 | Vmware, Inc. | Validation of desired software state image for hardware incompatibilities |
-
2023
- 2023-07-20 CN CN202310899861.7A patent/CN116795452B/en active Active
Patent Citations (43)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102890587A (en) * | 2012-10-24 | 2013-01-23 | 中山佳时光电科技有限公司 | Driver-free electronic whiteboard control device crossing operating system platforms |
| CN103530121A (en) * | 2013-10-15 | 2014-01-22 | 武汉邮电科学研究院 | Method of compatibility of multiple hardware platforms by RRU single software version |
| CN104881604A (en) * | 2014-02-27 | 2015-09-02 | 中兴通讯股份有限公司 | Method and apparatus for operating versions files |
| CN104268086A (en) * | 2014-09-05 | 2015-01-07 | 南车株洲电力机车研究所有限公司 | Chip identification method and chip compatibility method |
| CN104966022A (en) * | 2015-06-12 | 2015-10-07 | 浪潮电子信息产业股份有限公司 | Chain-of-trust construction method and device based on chip |
| CN104991872A (en) * | 2015-06-19 | 2015-10-21 | 上海卓易科技股份有限公司 | Method and apparatus for implementing driving of intelligent device on peripheral device |
| EP3118703A1 (en) * | 2015-07-13 | 2017-01-18 | Volvo Car Corporation | Safety stoppage device and method for safety stoppage of an autonomous vehicle |
| EP3411836A1 (en) * | 2016-02-03 | 2018-12-12 | OPERR Technologies, Inc. | Method and system for on-demand customized services |
| CN106227516A (en) * | 2016-07-13 | 2016-12-14 | 北京安控科技股份有限公司 | A kind of apparatus and method of network chip adaptive communications |
| CN106293824A (en) * | 2016-08-04 | 2017-01-04 | 青岛海信电器股份有限公司 | A kind of from the method and device processing chip upgrade |
| CN106648758A (en) * | 2016-11-30 | 2017-05-10 | 中国电子科技集团公司第五十八研究所 | Multi-core processor BOOT starting system and method |
| CN107015807A (en) * | 2017-04-06 | 2017-08-04 | 青岛海信宽带多媒体技术有限公司 | A kind of device drives management method |
| CN107423075A (en) * | 2017-08-28 | 2017-12-01 | 深圳传音控股有限公司 | The register method and user terminal of driving |
| CN108055212A (en) * | 2017-12-05 | 2018-05-18 | 锐捷网络股份有限公司 | A kind of method and device of compatible PSE chips |
| CN109981010A (en) * | 2017-12-28 | 2019-07-05 | 沈阳新松机器人自动化股份有限公司 | A kind of motor driven systems and method |
| CN108519932A (en) * | 2018-01-24 | 2018-09-11 | 中国电子信息产业集团有限公司第六研究所 | A kind of more performance testing tools based on homemade chip platform |
| CN108268414A (en) * | 2018-03-26 | 2018-07-10 | 福州大学 | SD card driver and its control method based on SPI mode |
| CN108631554A (en) * | 2018-03-28 | 2018-10-09 | 成都启臣微电子股份有限公司 | A kind of circuit of automatic adjusument output driving ability |
| CN110413501A (en) * | 2018-04-26 | 2019-11-05 | 腾讯科技（深圳）有限公司 | Browser compatibility test method, device, system and readable storage medium storing program for executing |
| CN108984031A (en) * | 2018-07-11 | 2018-12-11 | 深圳贝特莱电子科技股份有限公司 | A kind of method that touch chip supports a variety of touch screens |
| CN109191630A (en) * | 2018-08-04 | 2019-01-11 | 南京理工大学 | A kind of Intelligent door lock in hotel of NFC compatible bluetooth |
| CN109240751A (en) * | 2018-09-04 | 2019-01-18 | 广东小天才科技有限公司 | The outer boxing group compatibility method and electronic equipment of a kind of electronic equipment |
| CN109471661A (en) * | 2018-09-30 | 2019-03-15 | 西安霍威航空科技有限公司 | A kind of embedded board and driving automatic generation method |
| CN109614165A (en) * | 2018-12-04 | 2019-04-12 | 山东财经大学 | A kind of parallel operation method of the multi version of com component and device |
| CN109725575A (en) * | 2018-12-27 | 2019-05-07 | 南京熊猫电子股份有限公司 | The application system of compatible adaptive various field industrial bus communication |
| CN109726279A (en) * | 2018-12-30 | 2019-05-07 | 联想(北京)有限公司 | A kind of data processing method and device |
| CN110007857A (en) * | 2019-03-08 | 2019-07-12 | 北京星网锐捷网络技术有限公司 | A kind of life-span prediction method and device of flash chip |
| EP3716058A1 (en) * | 2019-03-28 | 2020-09-30 | Siemens Aktiengesellschaft | Method for operating a device with a new program code |
| CN110322842A (en) * | 2019-05-21 | 2019-10-11 | 合肥维信诺科技有限公司 | A kind of pixel-driving circuit and display device |
| CN110405759A (en) * | 2019-07-16 | 2019-11-05 | 大唐微电子技术有限公司 | A kind of chip control system |
| CN110716874A (en) * | 2019-09-25 | 2020-01-21 | 北京计算机技术及应用研究所 | Method for testing hardware compatibility of domestic operating system |
| CN110806891A (en) * | 2019-09-27 | 2020-02-18 | 武汉船舶通信研究所（中国船舶重工集团公司第七二二研究所） | Method and device for generating software version of embedded equipment |
| CN110750405A (en) * | 2019-10-28 | 2020-02-04 | 天津津航计算技术研究所 | Software compatibility method based on hardware board card identification |
| CN111061643A (en) * | 2019-12-24 | 2020-04-24 | 五八同城信息技术有限公司 | SDK cluster compatibility detection method and device, electronic equipment and storage medium |
| CN111427619A (en) * | 2020-03-26 | 2020-07-17 | 深圳市镭神智能系统有限公司 | Driver self-adaption method, device, updating method, equipment and system |
| CN111797402A (en) * | 2020-06-17 | 2020-10-20 | 北京世纪互联宽带数据中心有限公司 | Method, device and storage medium for detecting software vulnerability |
| CN112579181A (en) * | 2020-11-13 | 2021-03-30 | 麒麟软件有限公司 | Multi-GPU (graphics processing Unit) drive compatibility method in operating system |
| CN112835623A (en) * | 2021-01-21 | 2021-05-25 | 成都万创科技股份有限公司 | Device compatible device and method based on EEPROM |
| CN114253740A (en) * | 2021-07-12 | 2022-03-29 | 北京鲸鲮信息系统技术有限公司 | Protocol stack data transmission method and device based on Linux kernel |
| CN113961253A (en) * | 2021-09-29 | 2022-01-21 | 阿里巴巴（中国）有限公司 | Driver calling method and device, electronic equipment and storage medium |
| CN114237727A (en) * | 2021-12-21 | 2022-03-25 | 深圳市有方科技股份有限公司 | Drive loading method and device, computer equipment and storage medium |
| CN114510279A (en) * | 2022-01-28 | 2022-05-17 | 浙江大豪明德智控设备有限公司 | Device management method, device, electronic device, storage medium, and program product |
| CN116048640A (en) * | 2022-12-30 | 2023-05-02 | 深圳市创智成科技股份有限公司 | Method for driving IIC equipment in computer system to work normally |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116795452A (en) | 2023-09-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106598632B (en) | Firmware upgrading method and device for optical module | |
| US20140052403A1 (en) | Test system and test method thereof | |
| CN113849272A (en) | Method and device for adding GPU (graphics processing Unit) resources in virtual machine | |
| CN107145455B (en) | Method for updating SMBIOS static information of whole system | |
| US8463951B1 (en) | Unified driver architecture device identifier strategy | |
| CN111930395B (en) | Program downloading method of intelligent terminal and intelligent terminal | |
| US6904484B1 (en) | Low pin count (LPC) firmware hub recovery | |
| CN116795452B (en) | Method, device and equipment for determining compatibility of driving program | |
| CN103003033A (en) | Robot system control method and a device therefor | |
| CN113535262A (en) | Method, device, equipment and storage medium for controlling starting of proxy node | |
| CN116627513B (en) | Method and device for starting boot of computer | |
| US20190179788A1 (en) | Hot plugging of virtual bridges in a virtual pci system | |
| CN109445698B (en) | Method and device for querying multi-chip flash state and computer readable storage medium | |
| US11816058B2 (en) | Method for dynamically modifying PCH PCIE root port where onboard VGA is located | |
| CN111417908A (en) | ECU (electronic control Unit) recognizer, and recognition method, system, equipment and medium thereof | |
| CN111562907A (en) | Conversion method and system of user-defined interface data | |
| CN107864152B (en) | Method for rapidly completing intelligent building multi-protocol adaptation engineering template by using VBA | |
| CN108829574B (en) | Test data laying method, test server and computer readable storage medium | |
| CN111736858A (en) | Terminal equipment upgrading method, storage medium and terminal equipment | |
| CN115664953B (en) | Resource allocation method and related device of external equipment | |
| US20230333841A1 (en) | Electronic control apparatus, reprogram execution method, and non-transitory computer readable storage medium | |
| CN112306416B (en) | Method and terminal for automatically reading and writing NV (network video) parameters | |
| CN113794589B (en) | Packaging method of AC firmware, upgrading method of AP and AC | |
| CN111722870B (en) | Driving configuration method, device and equipment of electronic control unit and storage medium | |
| CN116400968A (en) | Method and device for starting embedded board card, central processing unit and embedded board card |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |