CN110795153A - Electronic equipment and hardware configuration method and device thereof - Google Patents
Electronic equipment and hardware configuration method and device thereof Download PDFInfo
- Publication number
- CN110795153A CN110795153A CN201910871551.8A CN201910871551A CN110795153A CN 110795153 A CN110795153 A CN 110795153A CN 201910871551 A CN201910871551 A CN 201910871551A CN 110795153 A CN110795153 A CN 110795153A
- Authority
- CN
- China
- Prior art keywords
- identifier
- software
- hardware
- loading
- electronic device
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 33
- 238000012545 processing Methods 0.000 claims description 13
- 230000036316 preload Effects 0.000 claims description 5
- 238000012423 maintenance Methods 0.000 abstract description 8
- 238000010586 diagram Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 7
- 230000003287 optical effect Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000005236 sound signal Effects 0.000 description 4
- 230000001133 acceleration Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
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/4411—Configuring for operating with peripheral devices; Loading of device drivers
-
- 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/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
Abstract
The application relates to an electronic device and a hardware configuration method and device thereof, which comprises the steps of storing driving software of at least one hardware module of various types and specifications available for the electronic device and a corresponding first device identifier in a system file of the electronic device, and then selecting the driving software corresponding to a second device identifier to be loaded according to the second device identifier of a hardware module to be loaded connected to the electronic device to load when the access of a new hardware module is detected, so that the loading work of the driving software related to the hardware module can be flexibly and efficiently realized, different service requirements can be met, and the maintenance cost of later-stage equipment can be reduced.
Description
Technical Field
The present application belongs to the field of electronic technologies, and in particular, to an electronic device and a hardware configuration method and apparatus thereof.
Background
As underlying technologies and device capabilities improve, portable electronic devices such as smart phones and tablet devices become more prevalent, and the functionality integrated by these electronic devices is becoming more abundant. These electronic devices include hardware modules that support various functions and applications, for example, current smart phones include hardware modules that support fingerprint recognition, infrared sensing, bluetooth, etc. functions. In the existing electronic device, each time a new hardware module is integrated, loading of configuration software such as driver software and middleware related to the hardware device in the hardware environment needs to be completed at the same time.
In consideration of cost control and quality guarantee, a plurality of manufacturers can be selected for the same type of hardware modules by the existing electronic equipment manufacturers, and most of configuration software of the hardware modules of different manufacturers is incompatible with each other. If different software systems are configured for each manufacturer's hardware module, the efficiency of hardware configuration is reduced, and the cost of later equipment maintenance is increased.
Disclosure of Invention
In order to overcome the problems in the related art, the application discloses an electronic device and a hardware configuration method and device thereof, which improve the loading efficiency of a loading process of a hardware module in the electronic device and improve the flexibility of the loading process so as to reduce the maintenance cost of the device in the later period.
According to a first aspect of embodiments of the present application, there is provided a hardware configuration method for an electronic device, including:
storing at least one driving software and a corresponding first device identifier thereof into a system file, wherein the driving software is used for driving a corresponding hardware module in the electronic device;
acquiring a second equipment identifier of the hardware module to be loaded; and
and determining and loading corresponding driving software from the system file according to the second equipment identifier.
Preferably, the determining and loading the corresponding driver software from the system file according to the second device identifier includes:
comparing the second device identification with the at least one first device identification, taking the first device identification which is the same as the second device identification as the device identification to be called, and
and loading the driving software corresponding to the identifier to be called.
Preferably, the determining and loading the corresponding driver software from the system file according to the second device identifier includes:
selecting a driving software from the system file for preloading;
comparing a first device identification of the selected driver software with the second device identification, and if the first device identification is the same as the second device identification, continuing to load the selected driver software; if not, quitting loading, and selecting one driving software from the rest driving software for preloading;
and repeating the steps until the driving software corresponding to the second equipment identification is determined from the system file.
Preferably, the first device identification and the second device identification include: a manufacturer number and/or a device number of the hardware module.
Preferably, the acquiring the second device identifier of the hardware module to be loaded includes:
and scanning and acquiring a second device identifier of a hardware module to be loaded connected with the electronic device when the electronic device is started each time.
According to a second aspect of the embodiments of the present application, there is provided a hardware configuration apparatus of an electronic device, including:
the storage unit is used for storing at least one piece of driving software and a corresponding first device identifier thereof, wherein the driving software is used for driving a corresponding hardware module in the electronic device;
the acquiring unit is used for acquiring a second equipment identifier of the hardware module to be loaded; and
and the loading unit is used for determining and loading the corresponding driving software according to the second equipment identifier.
Preferably, the loading unit includes: the hardware identification module is used for comparing the second equipment identifier with the at least one first equipment identifier and taking the first equipment identifier which is the same as the second equipment identifier as the equipment identifier to be called; and
and the processing module is used for loading the driving software corresponding to the identifier to be called.
Preferably, the loading unit includes: the recognizer is used for comparing a first device identifier of the driving software with a second device identifier when the corresponding driving software is in a pre-loading state, and if the first device identifier is the same as the second device identifier, the driving software continues to be loaded; and if not, quitting the loading.
Preferably, the loading unit sequentially selects one of the at least one driver software to preload until the driver software corresponding to the second device identifier is determined from the system file.
Preferably, the first device identification and the second device identification include: a manufacturer number and/or a device number of the hardware module.
Preferably, the obtaining unit scans and obtains a second device identifier of a hardware module to be loaded connected to the electronic device at each time of starting the electronic device.
According to a third aspect of embodiments of the present application, there is provided an electronic apparatus, including: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to perform the hardware configuration method described above.
The technical scheme provided by the embodiment of the application can have the following beneficial effects:
the method comprises the steps of firstly storing driving software of at least one hardware module of various types and specifications available for the electronic equipment and a corresponding first equipment identifier in a system file of the electronic equipment, and then selecting the driving software corresponding to a second equipment identifier to be loaded according to the second equipment identifier of a hardware module to be loaded connected to the electronic equipment to load when the access of a new hardware module is detected, so that the loading work of the driving software related to the hardware module can be flexibly and efficiently realized, different service requirements can be met, and the maintenance cost of the equipment in the later period can be reduced.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
Fig. 1 shows a software architecture diagram of an electronic device according to the prior art;
FIG. 2 illustrates a flow diagram of a method of hardware configuration according to an exemplary embodiment of the present application;
fig. 3 shows a software configuration diagram of an electronic device according to a first embodiment of the present application;
fig. 4 shows a software architecture diagram of an electronic device according to a second embodiment of the present application;
FIG. 5 illustrates a block diagram of a hardware configuration apparatus according to another exemplary embodiment of the present application;
fig. 6 shows a schematic structural diagram of an electronic device for the above hardware configuration method according to an exemplary embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
Fig. 1 shows a schematic diagram of a software architecture of an electronic device according to the prior art. As shown in fig. 1, the existing electronic device is implemented by, for example, an embedded system, and an embedded system apparatus generally includes an embedded computer system and an execution apparatus. The embedded computer system is the core of the whole embedded system and consists of a hardware layer, a middle layer, a system software layer and an application software layer. The execution device, also called a controlled object, can accept control commands from the embedded computer system and execute the specified operations or tasks.
The hardware layer includes a number of hardware structures such as embedded microprocessors, memory (SDRAM, ROM, FLASH, etc.), general device interfaces, and I/O interfaces (A/D, D/A, I/O, etc.). A power supply circuit, a clock circuit and a memory circuit are added on the basis of an embedded processor to form an embedded core control module, wherein an operating system and an application program can be solidified in a ROM. Hardware modules a and B as shown in fig. 1 are included in the hardware layer.
The architecture of the embedded microprocessor may employ a von Neumann architecture or a Harvard architecture; the Instruction system may be a Reduced Instruction Set Computer (RISC) or a Complex Instruction Set Computer (CISC).
The software architecture of the embedded system includes a driver software layer 110, a system component layer 120, and an application software layer 130. The driver software layer 110 is mainly used for device drivers related to hardware, and the driver software is used for indicating the device type, the manufacturer, the model, the file to be loaded, the target path to be loaded, and the like of the hardware module to be installed by the embedded system. In the system initialization process, the BSP (Board Support Package) of the middleware associates them with the general device driver in the operating system, and the BSP is called by the general device driver in the subsequent application to implement the operation of the hardware device. The system component layer 120 is responsible for allocation of all software and hardware resources of the embedded system, task scheduling, control and coordination of concurrent activities, and achieves functions required by the system by loading and unloading certain modules. The application layer 130 includes a plurality of application software corresponding to the system software, and is a collection of various programming languages that can be used by the user and application programs programmed in the various programming languages, which are divided into application packages and user programs.
In the prior art, each new hardware module needs to load its corresponding driver software. Taking the hardware module a as an example, firstly, a hardware manufacturer integrates the driver software a and the middleware of the hardware module a into a system file of the electronic device according to a set sequence, after an operating system of the electronic device is started, the system file can be automatically called, and when a command that the driver software a needs to be loaded is read, the driver software a pre-stored in the hard disk is read into a memory to complete loading work.
In consideration of cost control and quality guarantee, a plurality of manufacturers can be selected for the same type of hardware modules by the conventional electronic equipment manufacturers, and most of the driving software of the hardware modules of different manufacturers is incompatible with each other. If different software systems are configured for each manufacturer's hardware module, the efficiency of hardware configuration is reduced, and the cost of later equipment maintenance is increased.
In order to improve loading efficiency of a loading process of a hardware module in an electronic device and improve flexibility of the loading process to reduce maintenance cost of a later-stage device, embodiments of the present application provide a method and an apparatus for configuring hardware of an electronic device, which can store driver software of at least one hardware module connected to the electronic device and a first device identifier corresponding to the driver software in a system file of the electronic device, and select the driver software corresponding to a second device identifier to load according to the second device identifier of the hardware module connected to the electronic device.
For the purpose of facilitating an understanding of the present invention, the present invention will now be described in detail by way of specific examples, which are not intended to limit the present invention.
Fig. 2 shows a flow diagram of a hardware configuration method according to an exemplary embodiment of the present application, including the following steps:
step S101: and storing at least one driving software and a corresponding first device identifier thereof into a system file, wherein each driving software is used for driving a corresponding hardware module in the electronic device.
In this embodiment, according to different service requirements, the system software integrates the driver software of the hardware modules of different types and different specifications and the corresponding first device identifier into the electronic device, and generates an image file to be stored in a system file of the electronic device, so that the corresponding driver software is subsequently acquired from the system file to be loaded according to the specification of the actually connected hardware module. Compared with the prior art that the related driving software is required to be downloaded from the optical disc or the network side every time the hardware module is replaced, the time for obtaining the driving software can be saved, and the efficiency in the driving software loading process is improved.
The first device identifier includes identification information of the hardware module, such as a device number, a manufacturer number, and the like.
And S102, reading a register of a hardware module connected with the electronic equipment, and identifying a second equipment identifier of the hardware module to be loaded.
The hardware module connected to the electronic device may include a Peripheral Component Interconnect (PCI) device and a Universal Serial Bus (USB) device. The PCI device is a hardware module, such as a sound card, a network card, etc., connected to the electronic device through a PCI slot. The USB device is a hardware device connected to the electronic device through a USB interface, such as a mouse and a keyboard.
In addition, the hardware module connected to the electronic device may further include devices integrated inside the electronic device, such as a camera, an infrared sensor, an inertial sensor, a fingerprint recognition module, and the like. Or a device which wirelessly communicates with the electronic device, such as a bluetooth headset, a touch pen, etc.
In a specific embodiment, after the electronic device is powered on, the embedded operating system scans a hardware module to be loaded connected with the electronic device in a hardware environment at each start, and records a second device identifier of the hardware module. Similarly, the second device identifier also includes identification information of the hardware module, such as a device number, a manufacturer number, and the like.
Step S103: and determining and loading corresponding driving software from the system file according to the second equipment identifier.
In an embodiment, an operating system of an electronic device is configured with a hardware identification module, where the hardware identification module is configured to compare the obtained second device identifier with at least one first device identifier stored in a system file, use a first device identifier that is the same as the second device identifier as a device identifier to be called, and load driver software corresponding to the device identifier to be called.
In one embodiment, the at least one driver software is stored in a file system of the electronic device, and the embedded operating system reads the corresponding driver software from the file system to the memory according to the identifier to be called, and then calls and executes an initialization function in the driver software. In another embodiment, the at least one driver software is directly stored in the embedded operating system in a software form, and is stored in the memory of the electronic device together with the operating system, and the embedded operating system directly calls the corresponding driver software according to the identifier to be called and executes the initialization function of the driver software in the loading process.
Referring to fig. 3, a schematic diagram of a software structure of an electronic device according to a first embodiment of the present application is shown, and for convenience of description, the present embodiment is described by taking a hardware module a (i.e., a hardware module a1 and a hardware module a2) with two specifications as an example, but the present application is not limited to the present embodiment.
The electronic device includes a driver software layer 210, a system component layer 220, and an application software layer 230. The system component layer 220 and the application software layer 230 in this embodiment are the same as the system component layer 120 and the application software layer 130 in fig. 1, and are not described herein again. The difference between this embodiment and the electronic device in fig. 1 is that the driver software layer 210 further includes a hardware identification module 211, where the hardware identification module 211 is configured to compare the obtained second device identifier with at least one first device identifier stored in the system file, use a first device identifier that is the same as the second device identifier as a device identifier to be called, and load driver software corresponding to the device identifier to be called.
As shown in fig. 3, when the hardware module Ax (x may be 1 or 2) to be loaded is connected to the electronic device, the hardware identification module 211 obtains a second device identifier of the hardware module Ax to be loaded, and compares the second device identifier with the first device identifier corresponding to the driver software a1 and the first device identifier corresponding to the driver software a2, respectively, and when the second device identifier is the same as the first device identifier corresponding to the driver software a1, the hardware identification module 211 loads the driver software a 1; when the second device identification is the same as the first device identification corresponding to driver software a2, hardware identification module 211 loads driver software a 2.
In another embodiment, the embedded operating system selects a piece of driver software from the system file to preload, the selected driver software compares a first device identifier corresponding to the selected driver software with a second device identifier during preloading, and if the first device identifier is the same as the second device identifier, the loading is continuously completed; and if not, quitting loading, selecting one driving software from the rest driving software by the operating system for preloading, and repeating the steps until the loading of the hardware module to be loaded is completed.
Referring to fig. 4, a schematic diagram of a software structure of an electronic device according to a second embodiment of the present application is shown, and for convenience of description, the present embodiment is described by taking a hardware module a (i.e., a hardware module a1 and a hardware module a2) with two specifications as an example, but the present application is not limited to the present embodiment.
The electronic device includes a driver software layer 310, a system component layer 320, and an application software layer 330. The system component layer 320 and the application software layer 330 in this embodiment are the same as the system component layer 120 and the application software layer 130 in fig. 1, and are not described herein again. The present embodiment is different from the electronic device of fig. 1 in that the driver software layer 210 further includes at least one identifier (i.e., identifier a1 and identifier a 2). The recognizer and corresponding driving software are stored in a system file together, when one driving software is selected from the system file for preloading, the recognizer corresponding to the driving software is started firstly to obtain a second equipment identifier of a hardware module to be loaded, the first equipment identifier of the driving software is compared with the second equipment identifier, and if the first equipment identifier is the same as the second equipment identifier, the driving software is continuously loaded; and if not, quitting the loading.
As shown in fig. 4, when the hardware module Ax (x may be 1 or 2) to be loaded is connected to the electronic device, the operating system first preloads the driver software a1, and the identifier a1 compares the first device identifier corresponding to the driver software a1 with the second device identifier of the hardware module Ax to be loaded, and if the first device identifier and the second device identifier are the same, continues to load the driver software a 1; if the two are not the same, the driver A1 stops being loaded. The operating system then preloads driver software a2, and the above steps are repeated until the loading of the driver software of the hardware module Ax is completed.
In summary, in the embodiment of the present application, the driver software of at least one hardware module of various types and specifications available for the electronic device and the corresponding first device identifier are first stored in the system file of the electronic device, and then when detecting that a new hardware module is accessed, the driver software corresponding to the second device identifier is selected to be loaded according to the second device identifier of the hardware module to be loaded connected to the electronic device, so that the loading operation of the driver software related to the hardware module can be flexibly and efficiently implemented to adapt to different service requirements, and the maintenance cost of the device in the later period can be reduced.
Referring to fig. 4, a hardware configuration apparatus of an electronic device according to another exemplary embodiment of the present application is provided, which includes a storage unit 410, an obtaining unit 420, and a loading unit 430.
The storage unit 410 is configured to store at least one driving software and a corresponding first device identifier thereof, where the driving software is configured to drive a corresponding hardware module in the electronic device.
In this embodiment, according to different service requirements, the system software integrates the driver software of the hardware modules of different types and different specifications and the corresponding first device identifier into the electronic device, and generates an image file to be stored in a system file of the electronic device, so that the corresponding driver software is subsequently acquired from the system file to be loaded according to the specification of the actually connected hardware module. Compared with the prior art that the related driving software is required to be downloaded from the optical disc or the network side every time the hardware module is replaced, the time for obtaining the driving software can be saved, and the efficiency in the driving software loading process is improved.
The first device identifier includes identification information of the hardware module, such as a device number, a manufacturer number, and the like.
The obtaining unit 420 is configured to identify a second device identifier of the hardware module to be loaded by reading a register of the hardware module to be loaded connected to the electronic device.
In a specific embodiment, the obtaining unit 420 is configured to scan a hardware module connected to the electronic device in the hardware environment and record a second device identifier of the hardware module when the embedded operating system is started each time after the electronic device is powered on. Similarly, the second device identifier includes identification information of the hardware module, such as a device number, a manufacturer number, and the like.
The loading unit 430 is configured to determine and load corresponding driver software according to the second device identifier.
In an embodiment, the loading unit 430 includes a hardware identification module and a processing module, and is configured to compare the second device identifier with the at least one first device identifier, and use a first device identifier that is the same as the second device identifier as the device identifier to be called. And the processing module is used for loading the driving software corresponding to the identifier to be called.
In another embodiment, the loading unit 430 includes at least one identifier corresponding to at least one driver software, each identifier is configured to compare a first device identifier of the driver software with the second device identifier when the corresponding driver software is in a preloaded state, and if the first device identifier is the same as the second device identifier, continue to load the driver software; and if not, quitting the loading.
In a specific embodiment, the embedded operating system selects a piece of driving software from a system file for preloading, the identifier of the selected driving software reads the second equipment identifier of the hardware module during preloading, the second equipment identifier is compared with the first equipment identifier of the embedded operating system, and if the second equipment identifier is the same as the first equipment identifier of the embedded operating system, the embedded operating system continues to load; if the two are different, the loading is stopped. And the embedded operating system selects one driver software from the rest driver software for preloading. And repeating the steps until the loading of the driving software of the hardware module to be loaded is completed.
With regard to the apparatus in the above-described embodiment, the specific manner in which each unit performs the operation has been described in detail in the embodiment related to the method, and will not be described in detail here.
Fig. 6 is a schematic structural diagram of an electronic device 500 for the above-described hardware configuration method according to an exemplary embodiment. For example, the electronic device 500 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.
Referring to fig. 6, electronic device 500 may include one or more of the following components: processing component 505, memory 501, power component 502, multimedia component 503, audio component 504, input/output (I/O) interface 508, sensor component 507, and communication component 506.
The processing component 505 generally controls the overall operation of the device 500, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 505 may include one or more processors 510 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 505 may include one or more modules that facilitate interaction between the processing component 505 and other components. For example, the processing component 505 may include a multimedia module to facilitate interaction between the multimedia component 503 and the processing component 505.
The memory 501 is configured to store various types of data to support operations at the device 500. Examples of such data include instructions for any application or method operating on device 500, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 501 may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
In this embodiment, the driver software information of different types of hardware modules with different specifications may be integrated in the electronic device according to different service requirements, and an image file is generated to be stored in the memory 501 of the electronic device, so that the corresponding driver software information is subsequently acquired from the system file according to the specification of the actually connected hardware module and loaded.
The power supply component 502 provides power to the various components of the device 500. The power components 502 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the apparatus 500.
The multimedia component 503 comprises a screen providing an output interface between the device 500 and the user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 503 includes a front facing camera and/or a rear facing camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data when the device 500 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 504 is configured to output and/or input audio signals. For example, the audio component 504 includes a Microphone (MIC) configured to receive external audio signals when the apparatus 500 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in the memory 501 or transmitted via the communication component 506. In some embodiments, audio assembly 504 also includes a speaker for outputting audio signals.
The I/O interface 508 provides an interface between the processing component 505 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, an enable button, and a lock button.
The sensor assembly 507 includes one or more sensors for providing various aspects of condition assessment for the device 500. For example, the sensor assembly 507 may detect an open/closed state of the device 500, the relative positioning of components, such as a display and keypad of the apparatus 500, the sensor assembly 507 may also detect a change in position of the apparatus 500 or a component of the apparatus 500, the presence or absence of user contact with the apparatus 500, orientation or acceleration/deceleration of the apparatus 500, and a change in temperature of the apparatus 500. The sensor assembly 507 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 507 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 507 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 506 is configured to facilitate wired or wireless communication between the apparatus 500 and other devices. The apparatus 500 may access a wireless network based on a communication standard, such as WiFi, an operator network (such as 2G, 3G, 4G, or 5G), or a combination thereof. In an exemplary embodiment, the communication component 506 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 506 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the apparatus 500 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components, and is configured to perform the hardware configuration method, so that when a new hardware module is detected to be accessed, according to a second device identifier of a hardware module connected to an electronic device, driving software corresponding to the second device identifier is selected to be loaded, thereby flexibly and efficiently implementing loading work of the driving software related to the hardware module to adapt to different service requirements, and also reducing maintenance cost of a later device.
In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as the memory 501 including instructions executable by the processor 510 of the apparatus 500 to perform the above-described method. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
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 invention 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 invention 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 will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (12)
1. A method for configuring hardware of an electronic device, comprising:
storing at least one driving software and a corresponding first device identifier thereof into a system file, wherein the driving software is used for driving a corresponding hardware module in the electronic device;
acquiring a second equipment identifier of the hardware module to be loaded; and
and determining and loading corresponding driving software from the system file according to the second equipment identifier.
2. The hardware configuration method according to claim 1, wherein the determining and loading the corresponding driver software from the system file according to the second device identifier comprises:
comparing the second device identification with the at least one first device identification, taking the first device identification which is the same as the second device identification as the device identification to be called, and
and loading the driving software corresponding to the identifier to be called.
3. The hardware configuration method according to claim 1, wherein the determining and loading the corresponding driver software from the system file according to the second device identifier comprises:
selecting a driving software from the system file for preloading;
comparing a first device identification of the selected driver software with the second device identification, and if the first device identification is the same as the second device identification, continuing to load the selected driver software; if not, quitting loading, and selecting one driving software from the rest driving software for preloading;
and repeating the steps until the driving software corresponding to the second equipment identification is determined from the system file.
4. The hardware configuration method of claim 1, wherein the first device identification and the second device identification comprise: a manufacturer number and/or a device number of the hardware module.
5. The hardware configuration method according to claim 1, wherein the obtaining the second device identifier of the hardware module to be loaded comprises:
and scanning and acquiring a second device identifier of a hardware module to be loaded connected with the electronic device when the electronic device is started each time.
6. An apparatus for configuring hardware of an electronic device, comprising:
the storage unit is used for storing at least one piece of driving software and a corresponding first device identifier thereof, wherein the driving software is used for driving a corresponding hardware module in the electronic device;
the acquiring unit is used for acquiring a second equipment identifier of the hardware module to be loaded; and
and the loading unit is used for determining and loading the corresponding driving software according to the second equipment identifier.
7. The hardware configuration apparatus according to claim 6, wherein the loading unit comprises:
the hardware identification module is used for comparing the second equipment identifier with the at least one first equipment identifier and taking the first equipment identifier which is the same as the second equipment identifier as the equipment identifier to be called; and
and the processing module is used for loading the driving software corresponding to the identifier to be called.
8. The hardware configuration apparatus according to claim 6, wherein the loading unit comprises:
the recognizer is used for comparing a first device identifier of the driving software with a second device identifier when the corresponding driving software is in a pre-loading state, and if the first device identifier is the same as the second device identifier, the driving software continues to be loaded; and if not, quitting the loading.
9. The hardware configuration apparatus according to claim 8, wherein the loading unit sequentially selects one of the at least one driver software to preload until determining the driver software corresponding to the second device identifier from the system file.
10. The hardware configuration apparatus of claim 6, wherein the first device identifier and the second device identifier comprise: a manufacturer number and/or a device number of the hardware module.
11. The apparatus according to claim 6, wherein the obtaining unit scans and obtains the second device identifier of the hardware module to be loaded connected to the electronic device at each boot of the electronic device.
12. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to perform the hardware configuration method of any of the preceding claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910871551.8A CN110795153A (en) | 2019-09-16 | 2019-09-16 | Electronic equipment and hardware configuration method and device thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910871551.8A CN110795153A (en) | 2019-09-16 | 2019-09-16 | Electronic equipment and hardware configuration method and device thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110795153A true CN110795153A (en) | 2020-02-14 |
Family
ID=69427242
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910871551.8A Pending CN110795153A (en) | 2019-09-16 | 2019-09-16 | Electronic equipment and hardware configuration method and device thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110795153A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111722870A (en) * | 2020-06-10 | 2020-09-29 | 中国第一汽车股份有限公司 | Drive configuration method, device and equipment of electric control unit and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106663009A (en) * | 2014-07-10 | 2017-05-10 | 哈曼国际工业有限公司 | Operating system startup acceleration |
| CN107544818A (en) * | 2016-06-28 | 2018-01-05 | 北京小米移动软件有限公司 | The loading method and device of system software |
| CN107704282A (en) * | 2017-09-15 | 2018-02-16 | 北京东土科技股份有限公司 | A kind of loading method and device applied to embedded system |
-
2019
- 2019-09-16 CN CN201910871551.8A patent/CN110795153A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106663009A (en) * | 2014-07-10 | 2017-05-10 | 哈曼国际工业有限公司 | Operating system startup acceleration |
| CN107544818A (en) * | 2016-06-28 | 2018-01-05 | 北京小米移动软件有限公司 | The loading method and device of system software |
| CN107704282A (en) * | 2017-09-15 | 2018-02-16 | 北京东土科技股份有限公司 | A kind of loading method and device applied to embedded system |
Non-Patent Citations (1)
| Title |
|---|
| 张乃琳, 机械工业出版社 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111722870A (en) * | 2020-06-10 | 2020-09-29 | 中国第一汽车股份有限公司 | Drive configuration method, device and equipment of electric control unit and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105955765B (en) | Application preloading method and device | |
| CN107291626B (en) | Data storage method and device | |
| US9886264B2 (en) | Method and device for upgrading firmware | |
| CN104951335B (en) | The processing method and processing device of application program installation kit | |
| EP3046212B1 (en) | Method and apparatus for controlling charging of terminal device | |
| CN104484200A (en) | Method and device for updating firmware | |
| EP3173963B1 (en) | Unlocking method and apparatus, computer program and recording medium | |
| EP3015983B1 (en) | Method and device for optimizing memory | |
| CN105930213A (en) | Application running method and apparatus | |
| CN105246068A (en) | Method and device for selecting SIM (Subscriber Identity Module) card | |
| CN105183571A (en) | Function calling method and device | |
| US9678868B2 (en) | Method and device for optimizing memory | |
| EP3118729A1 (en) | Method and device for presenting tasks | |
| CN110795153A (en) | Electronic equipment and hardware configuration method and device thereof | |
| EP3758343B1 (en) | Method and device for controlling image acquisition component and storage medium | |
| CN104391742B (en) | Optimizing application method and apparatus | |
| US10558973B2 (en) | Method and apparatus for card activation | |
| US10671827B2 (en) | Method and device for fingerprint verification | |
| EP3736665A1 (en) | Method and device for controlling application and computer-readable storage medium | |
| CN110569037B (en) | Data writing method and device | |
| CN114047885A (en) | Writing method, device, equipment and medium for multi-type data | |
| CN108763906B (en) | Biological feature recognition method and device | |
| CN112631695A (en) | Data verification method and device, electronic equipment and storage medium | |
| CN107122213B (en) | Program running method and device | |
| CN111158748A (en) | Information acquisition method and device and storage medium |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20211126 Address after: Room 501, Jinqian block, 10 Hongyi Road, Xinwu District, Wuxi City, Jiangsu Province, 214028 Applicant after: Wuxi rongka Technology Co.,Ltd. Address before: 430000 No. 2-1, floor 4, zone 3, 3S geospatial information industry base, Wuda Science Park, Donghu New Technology Development Zone, Wuhan City, Hubei Province Applicant before: WUHAN RONGCARD INTELLIGENT INFORMATION TECHNOLOGY CO.,LTD. |
|
| TA01 | Transfer of patent application right | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200214 |
|
| RJ01 | Rejection of invention patent application after publication |