WO2018171570A1 - 一种终端开机过程的驱动程序加载方法及终端设备 - Google Patents

一种终端开机过程的驱动程序加载方法及终端设备 Download PDF

Info

Publication number
WO2018171570A1
WO2018171570A1 PCT/CN2018/079536 CN2018079536W WO2018171570A1 WO 2018171570 A1 WO2018171570 A1 WO 2018171570A1 CN 2018079536 W CN2018079536 W CN 2018079536W WO 2018171570 A1 WO2018171570 A1 WO 2018171570A1
Authority
WO
WIPO (PCT)
Prior art keywords
driver
terminal
list
candidate
stored
Prior art date
Application number
PCT/CN2018/079536
Other languages
English (en)
French (fr)
Inventor
宋彬
Original Assignee
捷开通讯(深圳)有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 捷开通讯(深圳)有限公司 filed Critical 捷开通讯(深圳)有限公司
Publication of WO2018171570A1 publication Critical patent/WO2018171570A1/zh
Priority to US16/576,800 priority Critical patent/US10871972B2/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/16—Sound input; Sound output
    • G06F3/167—Audio in a user interface, e.g. using voice commands for navigating, audio feedback
    • 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/44505—Configuring for program initiating, e.g. using registry, configuration files
    • G—PHYSICS
    • G10—MUSICAL INSTRUMENTS; ACOUSTICS
    • G10L—SPEECH ANALYSIS TECHNIQUES OR SPEECH SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING TECHNIQUES; SPEECH OR AUDIO CODING OR DECODING
    • G10L15/00—Speech recognition
    • G10L15/22—Procedures used during a speech recognition process, e.g. man-machine dialogue
    • G—PHYSICS
    • G10—MUSICAL INSTRUMENTS; ACOUSTICS
    • G10L—SPEECH ANALYSIS TECHNIQUES OR SPEECH SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING TECHNIQUES; SPEECH OR AUDIO CODING OR DECODING
    • G10L15/00—Speech recognition
    • G10L15/22—Procedures used during a speech recognition process, e.g. man-machine dialogue
    • G10L2015/223—Execution procedure of a spoken command

Definitions

  • the present invention relates to the field of terminals, and in particular, to a driver loading method and a terminal device for a booting process of a terminal.
  • the technical problem to be solved by the present invention is to provide a driver loading method and a terminal device for booting a terminal, which can improve the booting speed and improve the user experience.
  • a technical solution adopted by the present invention is to provide a driver loading method for a terminal booting process, the method comprising: receiving a booting instruction; reading a device list; and determining whether the device list includes a device associated with the device.
  • Driver if the device list contains a driver associated with the device, the device is matched with the associated driver; if the match is successful, the associated driver is loaded; if the device list does not contain the device associated with the device
  • the driver matches the device with the candidate drivers pre-stored by the terminal one by one; loads the candidate driver that matches the device successfully.
  • another technical solution adopted by the present invention is to provide a driver loading method for a terminal booting process, wherein the terminal includes at least one device that needs to load a driver during the booting process, and the method includes: receiving a booting Instruction; read the device list; determine if the device list contains the driver associated with the device; if the device list contains the driver associated with the device, load the associated driver.
  • the step of loading the associated driver includes: matching the device with the associated driver; if the match is successful, loading the associated driver.
  • the step of loading the associated driver further includes: if the matching is unsuccessful, matching the device with other candidate drivers pre-stored by the terminal one by one; loading and The device matches the successful candidate driver.
  • the method further includes: if the device list does not include a driver associated with the device, matching the device with the candidate driver pre-stored by the terminal one by one; loading the candidate driver that successfully matches the device.
  • the method further includes: associating the device with a candidate driver that matches successfully, and storing the device in a device list.
  • a terminal device including at least one device that needs to load a driver during booting, the terminal device further including a processor and the processor a coupled receiver and a memory, the memory for storing instructions executed by the processor; the receiver for receiving a boot command; the processor performing the following steps in response to the boot command: reading a device list; determining Whether the driver associated with the device is included in the device list; the associated driver is loaded when a driver associated with the device is included in the device list.
  • the terminal of the present invention includes at least one device that needs to load a driver during the booting process, and the terminal receives the booting command, reads the device list, and further determines whether the device list is included.
  • the driver associated with the device and after determining that the driver associated with the device is included in the device list, load the associated driver instead of loading the driver of all devices of the terminal to achieve the boot speed of the terminal.
  • the user experience is improved, and the terminal of the present invention can directly read the device list by using a tool without disassembling the machine, thereby improving the efficiency of the after-sales service.
  • FIG. 1 is a schematic flow chart of an embodiment of a method for loading a driver in a booting process of the terminal of the present invention
  • FIG. 2 is a schematic flow chart of another embodiment of a method for loading a driver in a booting process of the terminal of the present invention
  • FIG. 3 is a schematic structural diagram of a first implementation manner of a terminal device according to the present invention.
  • FIG. 4 is a schematic structural diagram of a second implementation manner of a terminal device according to the present invention.
  • FIG. 5 is a schematic structural diagram of a third implementation manner of a terminal device according to the present invention.
  • FIG. 6 is a schematic structural diagram of a fourth implementation manner of a terminal device according to the present invention.
  • FIG. 7 is a schematic structural diagram of a fifth implementation manner of a terminal device according to the present invention.
  • FIG. 8 is a schematic structural diagram of a sixth implementation manner of a terminal device according to the present invention.
  • FIG. 9 is a schematic structural diagram of a seventh embodiment of a terminal device according to the present invention.
  • FIG. 1 is a schematic flowchart of an embodiment of a method for loading a driver in a booting process of the present invention, wherein the terminal includes at least one device that needs to load a driver during the booting process. It should be noted that the method of the present invention is not limited to the sequence of the flow shown in FIG. 1 if substantially the same result is obtained. As shown in FIG. 1, the method includes the following steps:
  • the terminal device can be a smart TV, a smart TV terminal, a high-definition TV set-top box, a digital TV set-top box, a smart phone, a tablet computer, a notebook computer, a UMPC (Ultra-mobile) Personal Computer, Netbook, PDA (Personal Digital Assistant).
  • UMPC Ultra-mobile
  • Netbook Netbook
  • PDA Personal Digital Assistant
  • the power-on command generally refers to the terminal system detecting that the time when the user presses the power-on button of the terminal is greater than or equal to the threshold of the power-on time of the terminal system.
  • the boot time threshold of the terminal system may be a factory setting or a user-defined one.
  • the power-on command may also be a voice command, and the terminal system detects that the matching value of the user's voiceprint information and the voiceprint information pre-stored in the terminal system is greater than or equal to the matching threshold of the terminal system; the power-on command may also be a fingerprint command, and the terminal The system detects that the fingerprint information of the user matches the fingerprint information pre-stored in the terminal system.
  • the power-on command may not be a voice command and/or a fingerprint command.
  • the terminal system stores the user's voice information and/or fingerprint information, the user can use the voice command and/or the fingerprint command to boot.
  • the terminal receives the power-on command for the first time, and during the power-on process, the terminal has a step of selecting a boot device list before the power-on is completely turned on. In this step, the user can select during the boot process. A device that needs to be loaded with a drive. If the user does not select the boot device list, the terminal system can default to the factory settings and load all the devices on the drive terminal system.
  • S103 Determine whether the device associated with the device is included in the device list.
  • the driver included in the device specifically refers to that the driver of the device is obtained by searching for a corresponding driver in the mapping table, wherein the mapping table presets a mapping relationship between each corresponding driver and the device.
  • each device in the model list can be driven by the driver associated with that device.
  • the driver associated with that device There is a list of models for each device in the device list, and each device in the model list can be driven by the driver associated with that device.
  • one and/or a few specific types of devices may be driven by a driver associated with the device, either the default settings of the end system or the user's own settings.
  • the device that can load the driver during the boot process is an LCD (Liquid Crystal). Display, LCD), CTP (Capacitive Touch) Panel, capacitive touch screen), Fornt_Camera (front camera), Back_Camera (back camera), Gsensor (Gravity-sensor, gravity sensor), Msensor (Magnetic Sensor, magnetic sensor), Psensor (Proximity Sensor, distance sensor), Gyro (Gyroscope, gyroscope), Fingerprint (fingerprint reader) and other I2C (Inte-Integrated) Circuit, Peripheral) or SPI (Serial Peripheral) Interface, serial peripheral interface) devices.
  • LCD Liquid Crystal
  • Display LCD
  • CTP Capacitive Touch Panel
  • capacitive touch screen capacitive touch screen
  • Fornt_Camera front camera
  • Back_Camera back camera
  • Gsensor Gravity-sensor, gravity sensor
  • Msensor Magnetic Sensor, magnetic sensor
  • Psensor Proximity Sensor, distance sensor
  • Gyro
  • the devices in the device list can be LCD, CTP, Fornt_Camera, Back_Camera, Gsensor, Msensor, Psensor, Gyro, Fingerprint, and I2C or SPI devices.
  • the models that can support the load-driven LCD are: ILI9881C: TXD: HSD, HX8394F: TDT: HSD, HX8394F: CPT: EACHOPTO
  • models that can support the load driver CTP are: FT3327, MSG2840, HX8527, which can support the loading driver Fornt_Camera
  • the models are: GC2375: 2M: FF, SP2509: 2M: FF, OV5675: 5M: FF, GC5005: 5M: FF, can support the loading driver
  • Back_Camera models are: OV5675COB: 5M: AF, GC5005: 5M: AF, S5K4H8 : 8M: AF, OV88
  • the LCD has three models: ILI9881C: TXD: HSD, HX8394F: TDT: HSD, HX8394F: CPT: EACHOPTO, and the terminal system can set ILI9881C by default: TXD: HSD, HX8394F: TDT: HSD, HX8394F: CPT: EACHOPTO three types of LCD can be driven by the driver associated with the LCD; or, users can set the ILI9881C: TXD: HSD, HX8394F: TDT: HSD two models of LCD can be The LCD model HX8394F:CPT:EACHOPTO driven by the driver associated with the LCD cannot be driven by the driver associated with the LCD.
  • the LCD driver can be loaded normally during the startup of the terminal; if the LCD in the user's terminal system The model number is HX8394F: CPT: EACHOPTO, the LCD driver cannot be loaded during the booting process of the terminal.
  • the device and the candidate driver pre-stored in the terminal are matched one by one, that is, the driver and terminal of one model device in the model list are selected.
  • the pre-stored candidate drivers are matched one by one. If the match is still unsuccessful, the terminal will skip the device and match the driver of the next device. Further, after the terminal is powered on, the terminal reads the driver of the device and prompts the user whether the device driver needs to be added to the device list.
  • step S104 may be skipped according to the input specific control signal (for example, long pressing a certain button), and step S105 may be directly performed. That is, after judging that the driver list associated with the device is included in the device list, the driver associated with the device in the device list is not loaded, and the matching step of the device with other subsequent drivers is directly performed, thereby further saving booting. time.
  • the driver included in the device specifically refers to that the driver of the device is obtained by searching for a corresponding driver in the mapping table, wherein the mapping table presets a mapping relationship between each corresponding driver and the device.
  • the terminal may associate the device with the successfully matched candidate driver by default and store it in the device list; or prompt the user to associate the device with the candidate driver that matches the match successfully. And stored in the device list.
  • the terminal receives the boot command, reads the device list, and further determines whether the device list includes a driver associated with the device, and loads the associated driver after determining that the device list includes the driver associated with the device.
  • the driver instead of loading the driver of all the devices of the terminal, improves the boot speed of the terminal and improves the user experience; and the terminal can also directly read the device list by using the tool without disassembling the machine, thereby improving The efficiency of after-sales service.
  • FIG. 2 is a schematic flowchart diagram of another embodiment of a method for loading a driver in a booting process of the terminal of the present invention.
  • This embodiment is the step S104 in the above embodiment: if the device list includes a driver associated with the device, loading one of the specific embodiments of the associated driver, the method includes the following steps:
  • the driver of the device is matched with the associated driver.
  • the device since each device in the device list has a list of models, the device is matched to the associated driver, that is, the driver associated with each model device in the model list is associated with The driver is matched. Further, if the driver of one of the model devices in the model list can be successfully matched with the associated driver, the terminal will skip the other devices in the model list and match the next device.
  • loading is the process of reading useful programs on the hard disk into memory. Specifically, it is a process of reading the driver of the device after the matching is successfully read into the terminal memory.
  • each device in the device list has a model list
  • the drivers for each device in the model list can be driven by the driver associated with the device. Therefore, the device is matched to the associated driver, which is to match the drivers of each model of the device with the associated driver.
  • a driver of a certain type and/or a certain type of device can be obtained by searching for a corresponding driver in a mapping table, wherein the mapping table presets a mapping relationship between each corresponding driver and the device. If one of the models is not in the mapping table, the device of that model cannot be matched to the driver associated with the device. After the terminal device is powered on, the terminal device can alert the user whether to associate the device of the model with the driver associated with the device.
  • S205 Associate the device with a candidate driver that matches successfully, and store it in the device list.
  • the device may be associated with a successfully matched candidate driver, which may be a default operation performed in the internal system of the terminal, or may be a manual setting of the user.
  • the step of storing to the device list may be the default operation of the terminal or the manual setting of the user.
  • the terminal records information related to the model of the device and performs corresponding feedback.
  • the device is an LCD and the model of the LCD is D
  • the driver of the LCD-D cannot be matched with other candidate drivers pre-stored by the terminal, and the terminal records the LCD.
  • the driver of this model D cannot be matched with the driver pre-stored by the terminal and the relevant information is provided to the relevant personnel, for example, after-sales service personnel.
  • the device list can be read using a special tool without the terminal device disassembling.
  • the relevant staff can use a special tool to read the device list.
  • the terminal receives the boot command, reads the device list, and further determines whether the device list includes a driver associated with the device, and loads the associated driver after determining that the device list includes the driver associated with the device.
  • the driver instead of loading the driver of all the devices of the terminal, improves the boot speed of the terminal and improves the user experience; and the terminal can also directly read the device list by using the tool without disassembling the machine, thereby improving The efficiency of after-sales service.
  • FIG. 3 is a schematic structural diagram of a first embodiment of a terminal device according to the present invention.
  • the terminal device 30 is the terminal device in the foregoing embodiment, wherein the terminal device 30 includes at least one device that needs to load a driver during the booting process.
  • the terminal device 30 includes an instruction receiving module 31, a list reading module 32, a determining module 33, and a first loading module 34.
  • the instruction receiving module 31 is configured to receive a booting instruction.
  • the list reading module 32 is used to read the device list.
  • the determining module 33 is configured to determine whether the device associated with the device is included in the device list.
  • the first load module 34 is configured to load the associated driver when the driver associated with the device is included in the device list.
  • model list for each device in the device list, and the drivers for each device in the model list can be driven by the driver associated with that device.
  • the terminal receives the boot command, reads the device list, and further determines whether the device list includes a driver associated with the device, and loads the associated driver after determining that the device list includes the driver associated with the device.
  • the driver instead of loading the driver of all the devices of the terminal, improves the boot speed of the terminal and improves the user experience; and the terminal can also directly read the device list by using the tool without disassembling the machine, thereby improving The efficiency of after-sales service.
  • FIG. 4 is a schematic structural diagram of a second embodiment of a terminal device according to the present invention.
  • the first loading module 34 of the terminal device 30 of the present embodiment includes: a matching unit 341 and a first loading unit 342.
  • Matching unit 341 is used to match the device to the associated driver.
  • the first loading unit 342 is configured to load the associated driver when the matching is successful.
  • FIG. 5 is a schematic structural diagram of a third embodiment of the terminal device of the present invention.
  • the first loading module 34 of the terminal device 30 of the present embodiment further includes: a screening unit 343 and a second loading unit 344.
  • the screening unit 343 is configured to match the device to other candidate drivers pre-stored by the terminal one by one in the unsuccessful matching.
  • the second loading unit 344 is configured to load a candidate driver that successfully matches the device.
  • FIG. 6 is a schematic structural diagram of a fourth implementation manner of a terminal device according to the present invention.
  • the terminal device 30 of the present embodiment further includes: a storage module 35.
  • the storage module 35 is used to associate the device with a candidate driver that matches successfully and store it in the device list.
  • FIG. 7 is a schematic structural diagram of a fifth implementation manner of a terminal device according to the present invention.
  • the terminal device 70 of the present embodiment includes an instruction receiving module 71, a list reading module 72, a determining module 73, a screening module 74, and a second loading module 75.
  • the instruction receiving module 71 is configured to receive a booting instruction.
  • the list reading module 72 is for reading the device list.
  • the determining module 73 is configured to determine whether the device associated with the device is included in the device list.
  • the screening module 74 is configured to match the device to the candidate drivers pre-stored by the terminal one by one when the device associated with the device is not included in the device list.
  • the second loading module 75 is configured to load a candidate driver that successfully matches the device.
  • FIG. 8 is a schematic structural diagram of a fifth implementation manner of a terminal device according to the present invention.
  • the terminal device 70 of the present embodiment includes: a storage module 76.
  • the storage module 76 is used to associate the device with a candidate driver that matches successfully and store it in the device list.
  • the respective modules of the foregoing communication terminal 30/70 can respectively perform the corresponding steps in the foregoing method embodiments, and therefore, the modules are not described herein. For details, refer to the description of the corresponding steps.
  • the terminal receives the boot command, reads the device list, and further determines whether the device list includes a driver associated with the device, and loads the associated driver after determining that the device list includes the driver associated with the device.
  • the driver instead of loading the driver of all the devices of the terminal, improves the boot speed of the terminal and improves the user experience; and the terminal can also directly read the device list by using the tool without disassembling the machine, thereby improving The efficiency of after-sales service.
  • FIG. 9 is a schematic structural diagram of a sixth implementation manner of a terminal device according to the present invention.
  • the terminal device can perform the steps performed by the terminal device in the foregoing method.
  • the processing device 90 includes a processor 91, a memory 92 coupled to the processor 91, and a receiver 93.
  • the terminal 90 includes at least one device that needs to load a driver during the booting process.
  • the memory 92 is used to store an operating system, instructions executed by the processor 91, and received messages and the like.
  • the receiver 93 is configured to receive a power on command.
  • the processor 91 is configured to read the device list; determine whether the device list includes a driver associated with the device; and when the device list includes a driver associated with the device, load the associated driver.
  • the processor 91 is further configured to match the device with the associated driver and, if the matching is successful, load the associated driver.
  • the processor 91 is further configured to match the device to other candidate drivers pre-stored by the terminal one by one in the unsuccessful matching, and load the candidate driver that successfully matches the device.
  • the processor 91 is further configured to match the device to the candidate driver pre-stored by the terminal one by one when the driver list is not included in the device list, and load the candidate driver that successfully matches the device.
  • the processor 91 is further configured to associate the device with a candidate driver that matches successfully and store it in the device list.
  • the terminal receives the boot command, reads the device list, and further determines whether the device list includes a driver associated with the device, and loads the associated driver after determining that the device list includes the driver associated with the device.
  • the driver instead of loading the driver of all the devices of the terminal, improves the boot speed of the terminal and improves the user experience; and the terminal can also directly read the device list by using the tool without disassembling the machine, thereby improving The efficiency of after-sales service.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Human Computer Interaction (AREA)
  • Multimedia (AREA)
  • Computational Linguistics (AREA)
  • Acoustics & Sound (AREA)
  • General Health & Medical Sciences (AREA)
  • Stored Programmes (AREA)

Abstract

本发明公开了一种终端开机过程的驱动程序加载方法及终端设备，其中，所述终端包括至少一在开机过程中需加载驱动程序的器件，所述方法包括：接收开机指令；读取器件列表；判断器件列表中是否包含与器件相关联的驱动程序；若器件列表中包含与器件相关联的驱动程序，则加载相关联的驱动程序。通过上述方式，本发明能够提升开机速度，改善用户体验。

Description

一种终端开机过程的驱动程序加载方法及终端设备
【技术领域】
本发明涉及终端领域，特别是涉及一种终端开机过程的驱动程序加载方法及终端设备。
【背景技术】
近年来，随着智能终端产业的不断发展，人们对于各种智能终端的智能化要求也越来越高。一方面就导致了目前的终端设备中集成有越来越多的功能，使得终端设备内部系统复杂度也越来越高。另一方面由于为了避免某些元器件出现紧缺导致影响量产的情况，往往在设计上会要求兼容多种不同型号的器件。从而导致终端设备开机启动时需要花费更多的时间来加载这些器件对应的驱动软件，进而导致终端设备开机启动时间的增加，极大的影响了用户的体验性。
【发明内容】
本发明主要解决的技术问题是提供一种终端开机过程的驱动程序加载方法及终端设备，能够提升开机速度，改善用户体验。
为解决上述技术问题，本发明采用的一个技术方案是：提供一种终端开机过程的驱动程序加载方法，方法包括：接收开机指令；读取器件列表；判断器件列表中是否包含与器件相关联的驱动程序；若器件列表中包含与器件相关联的驱动程序，将器件与相关联的驱动程序进行匹配；若匹配成功，则加载相关联的驱动程序；若器件列表中不包含与器件相关联的驱动程序，则将器件与终端预先存储的候选驱动程序进行逐一匹配；加载与器件匹配成功的候选驱动程序。
为解决上述技术问题，本发明采用的又一个技术方案是：提供一种终端开机过程的驱动程序加载方法，其中，终端包括至少一在开机过程中需加载驱动程序的器件，方法包括：接收开机指令；读取器件列表；判断器件列表中是否包含与器件相关联的驱动程序；若器件列表中包含与器件相关联的驱动程序，则加载相关联的驱动程序。
其中，若器件列表中包含与器件相关联的驱动程序，则加载相关联的驱动程序的步骤包括：将器件与相关联的驱动程序进行匹配；若匹配成功，则加载相关联的驱动程序。
其中，若器件列表中包含与器件相关联的驱动程序，则加载相关联的驱动程序的步骤进一步包括：若匹配不成功，则将器件与终端预先存储的其他候选驱动程序进行逐一匹配；加载与器件匹配成功的候选驱动程序。
其中，进一步包括：若器件列表中不包含与器件相关联的驱动程序，则将器件与终端预先存储的候选驱动程序进行逐一匹配；加载与器件匹配成功的候选驱动程序。
其中，进一步包括：将器件与匹配成功的候选驱动程序进行关联，并存储至器件列表中。
为解决上述技术问题，本发明采用的另一个技术方案是：提供一种终端设备，包括至少一在开机过程中需加载驱动程序的器件，所述终端设备还包括处理器以及与所述处理器耦接的接收器和存储器，所述存储器用于存储所述处理器执行的指令；所述接收器用于接收开机指令；所述处理器响应所述开机指令执行以下步骤：读取器件列表；判断所述器件列表中是否包含与所述器件相关联的驱动程序；在所述器件列表中包含与所述器件相关联的驱动程序时，加载所述相关联的驱动程序。
本发明的有益效果是：区别于现有技术的情况，本发明的终端包括至少一在开机过程中需加载驱动程序的器件，终端接收开机指令，读取器件列表，进而判断器件列表中是否包含与器件相关联的驱动程序，并在判断器件列表中包含与器件相关联的驱动程序后，加载相关联的驱动程序，而不是对终端的全部器件的驱动程序进行加载，实现了终端开机速度的提升，改善了用户体验；而且本发明的终端亦可以在不拆机的情况下，利用工具直接读取器件列表，提高了售后服务的效率。
【附图说明】
图1是本发明终端开机过程的驱动程序加载方法一实施方式的流程示意图；
图2是本发明终端开机过程的驱动程序加载方法另一实施方式的流程示意图；
图3是本发明终端设备第一种实施方式的结构示意图；
图4是本发明终端设备第二种实施方式的结构示意图；
图5是本发明终端设备第三种实施方式的结构示意图；
图6是本发明终端设备第四种实施方式的结构示意图；
图7是本发明终端设备第五种实施方式的结构示意图；
图8是本发明终端设备第六种实施方式的结构示意图；
图9是本发明终端设备第七种实施方式的结构示意图。
【具体实施方式】
请参阅图1，图1是本发明终端开机过程的驱动程序加载方法一实施方式的流程示意图，其中，终端包括至少一个在开机过程中需加载驱动程序的器件。需注意的是，若有实质上相同的结果，本发明的方法并不以图1所示的流程顺序为限。如图1所示，该方法包括如下步骤：
S101：接收开机指令。
其中，终端设备可以为智能电视、智能电视终端、高清电视机顶盒、数字电视机顶盒、智能手机、平板电脑、笔记本电脑、UMPC（Ultra-mobile Personal Computer，超级移动个人计算机）、上网本、PDA（Personal Digital Assistant，个人数字助理）等。
其中，开机指令一般是指终端系统检测到用户按终端开机键的时间大于等于终端系统的开机时间阈值。可选地，终端系统的开机时间阈值可以是出厂设置，也可以是用户自定义的。可选地，开机指令还可以是声音指令，终端系统检测到用户的声纹信息与终端系统内预存的声纹信息的匹配值大于等于终端系统的匹配阈值；开机指令还可以是指纹指令，终端系统检测到用户的指纹信息与终端系统内预存的指纹信息相匹配。需要说明的是，在终端首次进行开机时，开机指令不可以是声音指令和/或者指纹指令。在终端首次开机后，终端系统存储了用户的声音信息和/或者指纹信息之后，用户才可以利用声音指令和/或者指纹指令进行开机。
S102：读取器件列表。
其中，需要进行说明的是，在终端首次接收到开机指令，并在开机的过程中，终端在完全开机之前会有一个开机器件列表选择的步骤，在此步骤中，用户可以选择在开机过程中需要进行加载驱动的器件。若用户不进行开机器件列表的选择，则终端系统可以默认出厂设置，加载驱动终端系统上所有的器件。
S103：判断器件列表中是否包含与器件相关联的驱动程序。
其中，包含与器件相关联的驱动程序具体是指，器件的驱动程序是在映射表中查找对应的驱动程序而得到，其中，映射表预设各个对应的驱动程序与器件的映射关系。
S104：若器件列表中包含与器件相关联的驱动程序，则加载相关联的驱动程序。
其中，器件列表中的每一个器件均有一个型号列表，该型号列表中的每一个型号的器件均可以被与该器件相关联的驱动程序所驱动。可选地，某一个和/或某几个具体的型号器件可以被与该器件相关联的驱动程序所驱动，可以是终端系统的默认设置，还可以是用户自己的设置。
具体地，在开机过程中可以进行加载驱动程序的器件有为LCD（Liquid Crystal Display，液晶显示屏）、CTP（Capacitive Touch Panel，电容式触摸屏）、Fornt_Camera（前置相机）、Back_Camera（后置相机）、Gsensor（Gravity-sensor，重力感应器）、Msensor（Magnetic Sensor，磁力感应器）、Psensor（Proximity Sensor，距离感应器）、Gyro（Gyroscope，陀螺仪）、Fingerprint（指纹识别器）以及其他I2C（Inte-Integrated Circuit，外围设备）或SPI（Serial Peripheral interface，串行外围设备接口）设备等。因此，器件列表中的器件可以是LCD、CTP、Fornt_Camera、Back_Camera、Gsensor、Msensor、Psensor、Gyro、Fingerprint以及I2C或SPI设备等。具体地，可以支持加载驱动LCD的型号有：ILI9881C:TXD:HSD、HX8394F:TDT:HSD、HX8394F:CPT:EACHOPTO，可以支持加载驱动CTP的型号有：FT3327、MSG2840、HX8527，可以支持加载驱动Fornt_Camera的型号有：GC2375:2M:FF、SP2509:2M:FF、OV5675:5M:FF、GC5005:5M:FF，可以支持加载驱动Back_Camera的型号有：OV5675COB:5M:AF、GC5005:5M:AF、S5K4H8:8M:AF、OV8856:8M:AF、OV13858:13M:AF，可以支持加载驱动Gsensor的型号有：MXC4005XC、KXTJ2-1009、mc3413-p、BMA253，可以支持加载驱动Msensor的型号有：AKM09916、AKM09918、bmc156，可以支持加载Psensor的型号有：STK3311-W34、EPL2570，可以支持加载驱动Gyro的型号有：BMG160、BMG250，可以支持加载驱动Fingerprint的型号有：GF3208、FT9339、A112N。
在一个具体的实施方式中，以LCD为例，LCD有ILI9881C:TXD:HSD、HX8394F:TDT:HSD、HX8394F:CPT:EACHOPTO三种型号，终端系统可以默认地设置ILI9881C:TXD:HSD、HX8394F:TDT:HSD、HX8394F:CPT:EACHOPTO三种型号的LCD均可以被与LCD相关联的驱动程序所驱动；或者，用户可以设置ILI9881C:TXD:HSD、HX8394F:TDT:HSD两种型号的LCD可以被与LCD相关联的驱动程序所驱动，型号为HX8394F:CPT:EACHOPTO的LCD不可以被与LCD相关联的驱动程序所驱动。此时，若用户的终端系统的LCD的型号为ILI9881C:TXD:HSD或者HX8394F:TDT:HSD，则在终端开机的过程中，LCD的驱动程序可以被正常加载；若用户的终端系统中的LCD的型号为HX8394F:CPT:EACHOPTO，则在终端开机的过程中，LCD的驱动程序则不能被加载。
S105：若器件列表中不包含与器件相关联的驱动程序，则将器件与终端预先存储的候选驱动程序进行逐一匹配。
其中，由于器件列表中的每一个器件均有一个型号列表，因此，将器件与终端预先存储的候选驱动程序进行逐一匹配，也即是，将型号列表中的某一个型号器件的驱动程序与终端预先存储的候选驱动程序进行逐一匹配。若还是匹配不成功，则终端会跳过该器件，对下一个器件的驱动程序进行匹配。进一步地，在终端开机之后，终端会读取该器件的驱动程序，并提示用户，是否需要把器件的驱动程序加入器件列表中。
S106：加载与器件匹配成功的候选驱动程序。
具体地，在其中一个实施方式中，若是用户的终端设备进行了返修，把其中的某一个器件替换成了由不同驱动程序进行驱动的其他器件时，则终端设备内的器件列表中的所记录和关联的驱动程序已经不能正常驱动替换后的器件。此时，可根据输入的特定控制信号（例如长按某一特定按键）跳过步骤S104，直接进行步骤S105。即在判断器件列表中包含与该器件相关联的驱动程序后，不加载器件列表中与该器件相关联的驱动程序，而直接进行该器件与其他后续驱动程序的匹配步骤，由此进一步节约开机时间。
其中，包含与器件相关联的驱动程序具体是指，器件的驱动程序是在映射表中查找对应的驱动程序而得到，其中，映射表预设各个对应的驱动程序与器件的映射关系。
S107：将器件与匹配成功的候选驱动程序进行关联，并存储至器件列表中。
具体地，在终端开机成功后，终端可以默认地将器件与匹配成功的候选驱动程序进行关联，并存储至器件列表中；也可以提示用户，是否将器件与匹配成功的候选驱动程序进行关联，并存储至器件列表中。
本实施方式中，终端接收开机指令，读取器件列表，进而判断器件列表中是否包含与器件相关联的驱动程序，并在判断器件列表中包含与器件相关联的驱动程序后，加载相关联的驱动程序，而不是对终端的全部器件的驱动程序进行加载，实现了终端开机速度的提升，改善了用户体验；而且终端亦可以在不拆机的情况下，利用工具直接读取器件列表，提高了售后服务的效率。
请参阅图2，图2是本发明终端开机过程的驱动程序加载方法另一实施方式的流程示意图。本实施方式是上述实施方式中的步骤S104：若器件列表中包含与器件相关联的驱动程序，则加载相关联的驱动程序的其中一个具体的实施方式，该方法包括以下步骤：
S201：将器件与相关联的驱动程序进行匹配。
其中，将器件的驱动程序与相关联的驱动程序进行匹配。
具体地，由于器件列表中的每一个器件均有一个型号列表，因此，将器件与相关联的驱动程序进行匹配，也即是，将型号列表中的每一个型号器件的驱动程序与相关联的驱动程序进行匹配。进一步地，若是型号列表中的某一个型号器件的驱动程序与相关联的驱动程序可以匹配成功，则终端会跳过该型号列表中的其他型号器件，与下一个器件进行匹配。
S202：若匹配成功，则加载相关联的驱动程序。
其中，加载就是把硬盘上的有用程序读取到内存中的过程。具体地，也即是把匹配成功后的器件的驱动程序读取到终端内存中的过程。
S203：若匹配不成功，则将器件与终端预先存储的其他候选驱动程序进行逐一匹配。
可如上S105所述，在此不作赘述。
S204：加载与器件匹配成功的候选驱动程序。
其中，由于器件列表中的每一个器件均有一个型号列表，该型号列表中的每一个型号的器件的驱动程序均可以被与该器件相关联的驱动程序所驱动。因此，将器件与相关联的驱动程序进行匹配，也即是将器件的各个型号的驱动程序与相关联的驱动程序进行匹配。具体地，某一个和/或某几个型号的器件的驱动程序是可以在映射表中查找对应的驱动程序而得到的，其中，映射表预设各个对应的驱动程序与器件的映射关系。若其中一个型号的器件不在该映射表中，则该型号的器件就不可以与该器件相关联的驱动程序进行匹配。在终端设备开机之后，终端设备可以提醒用户是否把该型号的器件与该器件相关联的驱动程序进行相关联。
S205：将器件与匹配成功的候选驱动程序进行关联，并存储至器件列表中。
具体地，该器件与匹配成功的候选驱动程序进行关联可以是在终端内部系统中进行的默认操作，也可以是用户的手动设置。该器件与匹配成功的候选驱动程序进行关联之后，存储至器件列表的步骤，可以是终端的默认操作，也可以是用户的手动设置。
进一步地，若是该器件的型号列表中的某一个型号与终端设备预先存储的其他候选驱动程序均不能进行匹配，则终端会记录下与该器件的型号相关的信息，并进行相应的反馈。具体地，在其中一个具体的应用场景中，若该器件为LCD，LCD的型号为D，LCD-D的驱动程序与终端预先存储的其他候选驱动程序均不能进行匹配，则终端会记录LCD的这个型号D的驱动程序不能与终端预存的驱动程序进行匹配，并将相关的信息提供给相关的人员，例如，售后维修人员。
进一步地，在其中一个实施方式中，在终端设备不进行拆机的情况下，器件列表可以使用特殊工具读取出来。当器件列表中的器件既不能与相关联的驱动程序进行匹配，也不能与候选驱动程序进行匹配时，相关工作人员便可以使用特殊工具读取器件列表。
本实施方式中，终端接收开机指令，读取器件列表，进而判断器件列表中是否包含与器件相关联的驱动程序，并在判断器件列表中包含与器件相关联的驱动程序后，加载相关联的驱动程序，而不是对终端的全部器件的驱动程序进行加载，实现了终端开机速度的提升，改善了用户体验；而且终端亦可以在不拆机的情况下，利用工具直接读取器件列表，提高了售后服务的效率。
请参阅图3，图3是本发明终端设备第一种实施方式的结构示意图。本实施方式中，该终端设备30为上述实施方式中的终端设备，其中，该终端设备30包括至少一在开机过程中需加载驱动程序的器件。该终端设备30包括：指令接收模块31、列表读取模块32、判断模块33以及第一加载模块34。
指令接收模块31用于接收开机指令。
列表读取模块32用于读取器件列表。
判断模块33用于判断器件列表中是否包含与器件相关联的驱动程序。
第一加载模块34用于在器件列表中包含与器件相关联的驱动程序时，加载相关联的驱动程序。
其中，器件列表中的每一个器件均有一个型号列表，该型号列表中的每一个型号的器件的驱动程序均可以被与该器件相关联的驱动程序所驱动。
本实施方式中，终端接收开机指令，读取器件列表，进而判断器件列表中是否包含与器件相关联的驱动程序，并在判断器件列表中包含与器件相关联的驱动程序后，加载相关联的驱动程序，而不是对终端的全部器件的驱动程序进行加载，实现了终端开机速度的提升，改善了用户体验；而且终端亦可以在不拆机的情况下，利用工具直接读取器件列表，提高了售后服务的效率。
请参阅图4，图4是本发明终端设备第二种实施方式的结构示意图。区别于上一实施方式，本实施方式的终端设备30的第一加载模块34包括：匹配单元341以及第一加载单元342。
匹配单元341用于将器件与相关联的驱动程序进行匹配。
第一加载单元342用于在匹配成功时，加载相关联的驱动程序。
请参阅图5，图5是本发明终端设备第三种实施方式的结构示意图。区别于上一实施方式，本实施方式的终端设备30的第一加载模块34还包括：筛选单元343以及第二加载单元344。
筛选单元343用于在匹配不成功，将器件与终端预先存储的其他候选驱动程序进行逐一匹配。
第二加载单元344用于加载与器件匹配成功的候选驱动程序。
请参阅图6，图6是本发明终端设备第四种实施方式的结构示意图。区别于上一实施方式，本实施方式的终端设备30还包括：存储模块35。
存储模块35用于将器件与匹配成功的候选驱动程序进行关联，并存储至器件列表中。
请参阅图7，图7是本发明终端设备第五种实施方式的结构示意图。区别于上一实施方式，本实施方式的终端设备70包括：指令接收模块71、列表读取模块72、判断模块73、筛选模块74以及第二加载模块75。
指令接收模块71用于接收开机指令。
列表读取模块72用于读取器件列表。
判断模块73用于判断器件列表中是否包含与器件相关联的驱动程序。
筛选模块74用于在器件列表中不包含与器件相关联的驱动程序时，将器件与终端预先存储的候选驱动程序进行逐一匹配。
第二加载模块75用于加载与器件匹配成功的候选驱动程序。
请参阅图8，图8是本发明终端设备第五种实施方式的结构示意图。区别于上面的实施方式，本实施方式的终端设备70包括：存储模块76。
存储模块76用于将器件与匹配成功的候选驱动程序进行关联，并存储至器件列表中。
上述通信终端30/70的各个模块可分别执行上述方法实施方式中对应步骤，故在此不对各模块进行赘述，详细请参阅以上对应步骤的说明。
本实施方式中，终端接收开机指令，读取器件列表，进而判断器件列表中是否包含与器件相关联的驱动程序，并在判断器件列表中包含与器件相关联的驱动程序后，加载相关联的驱动程序，而不是对终端的全部器件的驱动程序进行加载，实现了终端开机速度的提升，改善了用户体验；而且终端亦可以在不拆机的情况下，利用工具直接读取器件列表，提高了售后服务的效率。
请参阅图9，图9是本发明终端设备第六种实施方式的结构示意图。该终端设备可以执行上述方法中终端设备执行的步骤，相关内容请参见上述方法中的详细说明，在此不再赘叙。
本实施方式中，该处理装置90包括：处理器91、与处理器91耦接的存储器92以及接收器93。其中，终端90包括至少一在开机过程中需加载驱动程序的器件，
存储器92用于存储操作系统、处理器91执行的指令以及接收到的消息等。
接收器93用于接收开机指令。
处理器91用于读取器件列表；判断器件列表中是否包含与器件相关联的驱动程序；在器件列表中包含与器件相关联的驱动程序时，加载相关联的驱动程序。
其中，处理器91还用于将器件与相关联的驱动程序进行匹配，并在匹配成功，加载相关联的驱动程序。
可选地，处理器91还用于在匹配不成功，将器件与终端预先存储的其他候选驱动程序进行逐一匹配，并加载与器件匹配成功的候选驱动程序。
可选地，处理器91还用于在器件列表中不包含与器件相关联的驱动程序时，将器件与终端预先存储的候选驱动程序进行逐一匹配，并加载与器件匹配成功的候选驱动程序。
进一步地，处理器91还用于将器件与匹配成功的候选驱动程序进行关联，并存储至器件列表中。
本实施方式中，终端接收开机指令，读取器件列表，进而判断器件列表中是否包含与器件相关联的驱动程序，并在判断器件列表中包含与器件相关联的驱动程序后，加载相关联的驱动程序，而不是对终端的全部器件的驱动程序进行加载，实现了终端开机速度的提升，改善了用户体验；而且终端亦可以在不拆机的情况下，利用工具直接读取器件列表，提高了售后服务的效率。
以上所述仅为本发明的实施方式，并非因此限制本发明的专利范围，凡是利用本发明说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本发明的专利保护范围内。

Claims (20)

  1. 一种终端开机过程的驱动程序加载方法，其中，所述终端包括至少一在所述开机过程中需加载驱动程序的器件，所述方法包括：
    接收开机指令；
    读取器件列表；
    判断所述器件列表中是否包含与所述器件相关联的驱动程序；
    若所述器件列表中包含与所述器件相关联的驱动程序，将所述器件与所述相关联的驱动程序进行匹配；
    若匹配成功，则加载所述相关联的驱动程序;
    若所述器件列表中不包含与所述器件相关联的驱动程序，则将所述器件与所述终端预先存储的候选驱动程序进行逐一匹配；
    加载与所述器件匹配成功的候选驱动程序。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    将所述器件与所述匹配成功的候选驱动程序进行关联，并存储至所述器件列表中。
  3. 一种终端开机过程的驱动程序加载方法，其中，所述终端包括至少一在所述开机过程中需加载驱动程序的器件，所述方法包括：
    接收开机指令；
    读取器件列表；
    判断所述器件列表中是否包含与所述器件相关联的驱动程序；
    若所述器件列表中包含与所述器件相关联的驱动程序，则加载所述相关联的驱动程序。
  4. 根据权利要求3所述的方法，其中，所述若所述器件列表中包含与所述器件相关联的驱动程序，则加载所述相关联的驱动程序的步骤包括：
    将所述器件与所述相关联的驱动程序进行匹配；
    若匹配成功，则加载所述相关联的驱动程序。
  5. 根据权利要求4所述的方法，其中，所述若所述器件列表中包含与所述器件相关联的驱动程序，则加载所述相关联的驱动程序的步骤进一步包括：
    若匹配不成功，则将所述器件与所述终端预先存储的其他候选驱动程序进行逐一匹配；
    加载与所述器件匹配成功的候选驱动程序。
  6. 根据权利要求5所述的方法，其中，所述方法进一步包括：
    将所述器件与所述匹配成功的候选驱动程序进行关联，并存储至所述器件列表中。
  7. 根据权利要求3所述的方法，其中，所述方法进一步包括：
    若所述器件列表中不包含与所述器件相关联的驱动程序，则将所述器件与所述终端预先存储的候选驱动程序进行逐一匹配；
    加载与所述器件匹配成功的候选驱动程序。
  8. 根据权利要求7所述的方法，其中，所述方法进一步包括：
    将所述器件与所述匹配成功的候选驱动程序进行关联，并存储至所述器件列表中。
  9. 根据权利要求3所述的方法，其中，所述开机指令为所述终端检测到用户按所述终端开机键的时间大于等于所述终端的开机时间阈值时而生成的指令。
  10. 根据权利要求3所述的方法，其中，所述开机指令为声音指令，所述开机指令为所述终端检测到用户的声纹信息与所述终端内预存的声纹信息的匹配值大于等于所述终端的匹配阈值时而生成的指令。
  11. 根据权利要求3所述的方法，其中，所述开机指令为指纹指令，所述开机指令为所述终端检测到用户的指纹信息与所述终端内预存的指纹信息相匹配时而生成的指令。
  12. 根据权利要求3所述的方法，其中，所述器件为液晶显示屏、前置相机、后置相机、传感器、电容式触摸屏或串行外围设备接口等中的任一个。
  13. 一种终端设备，其中，包括至少一在开机过程中需加载驱动程序的器件，所述终端设备还包括处理器以及与所述处理器耦接的接收器和存储器，所述存储器用于存储所述处理器执行的指令；
    所述接收器用于接收开机指令；
    所述处理器响应所述开机指令执行以下步骤：
    读取器件列表；
    判断所述器件列表中是否包含与所述器件相关联的驱动程序；
    在所述器件列表中包含与所述器件相关联的驱动程序时，加载所述相关联的驱动程序。
  14. 根据权利要求13所述的终端设备，其中，所述在所述器件列表中包含与所述器件相关联的驱动程序时，加载所述相关联的驱动程序的步骤包括：
    将所述器件与所述相关联的驱动程序进行匹配；并在匹配成功时，加载所述相关联的驱动程序。
  15. 根据权利要求14所述的终端设备，其中，所述在所述器件列表中包含与所述器件相关联的驱动程序时，加载所述相关联的驱动程序的步骤进一步包括：
    在匹配不成功时，将所述器件与所述终端预先存储的其他候选驱动程序进行逐一匹配；并加载与所述器件匹配成功的候选驱动程序。
  16. 根据权利要求15所述的终端设备，其中，所述处理器进一步执行以下步骤：
    将所述器件与所述匹配成功的候选驱动程序进行关联，并存储至所述器件列表中。
  17. 根据权利要求13所述的终端设备，其中，所述处理器进一步执行以下步骤：
    在所述器件列表中不包含与所述器件相关联的驱动程序时，将所述器件与所述终端预先存储的候选驱动程序进行逐一匹配；并加载与所述器件匹配成功的候选驱动程序。
  18. 根据权利要求17所述的终端设备，其中，所述处理器进一步执行以下步骤：
    将所述器件与所述匹配成功的候选驱动程序进行关联，并存储至所述器件列表中。
  19. 根据权利要求13所述的终端设备，其中，所述器件为液晶显示屏、前置相机、后置相机、传感器、电容式触摸屏或串行外围设备接口等中的任一个。
  20. 根据权利要求13所述的终端设备，其中，所述终端设备为智能电视或电视机顶盒或智能手机或平板电脑或笔记本电脑。
PCT/CN2018/079536 2017-03-21 2018-03-20 一种终端开机过程的驱动程序加载方法及终端设备 WO2018171570A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/576,800 US10871972B2 (en) 2017-03-21 2019-09-20 Method for loading driver during terminal starting up and terminal device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710169587.2 2017-03-21
CN201710169587.2A CN107145363A (zh) 2017-03-21 2017-03-21 一种终端开机过程的驱动程序加载方法及终端设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/576,800 Continuation US10871972B2 (en) 2017-03-21 2019-09-20 Method for loading driver during terminal starting up and terminal device

Publications (1)

Publication Number Publication Date
WO2018171570A1 true WO2018171570A1 (zh) 2018-09-27

Family

ID=59783991

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/079536 WO2018171570A1 (zh) 2017-03-21 2018-03-20 一种终端开机过程的驱动程序加载方法及终端设备

Country Status (3)

Country Link
US (1) US10871972B2 (zh)
CN (1) CN107145363A (zh)
WO (1) WO2018171570A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107145363A (zh) 2017-03-21 2017-09-08 捷开通讯(深圳)有限公司 一种终端开机过程的驱动程序加载方法及终端设备
CN109745699A (zh) * 2018-12-29 2019-05-14 维沃移动通信有限公司 一种响应触控操作的方法及终端设备
CN114398108A (zh) * 2020-08-29 2022-04-26 华为技术有限公司 电子设备及其驱动加载方法、介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1979416A (zh) * 2005-12-09 2007-06-13 英业达股份有限公司 驱动程序加载系统及方法
CN102510531A (zh) * 2011-10-20 2012-06-20 山东泰信电子有限公司 一种自动识别数字电视机顶盒调谐器和解调器的方法
CN103942078A (zh) * 2014-04-30 2014-07-23 华为技术有限公司 一种加载驱动程序的方法及嵌入式设备
CN104932918A (zh) * 2015-06-02 2015-09-23 惠州Tcl移动通信有限公司 移动终端及其lcd驱动程序的加载方法
CN107145363A (zh) * 2017-03-21 2017-09-08 捷开通讯(深圳)有限公司 一种终端开机过程的驱动程序加载方法及终端设备

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100697416B1 (ko) * 2003-09-30 2007-03-20 교세라 가부시키가이샤 모바일 통신 단말기, 정보 제공 시스템 및 프로그램을기록한 컴퓨터 판독가능한 기록 매체
CN102134110A (zh) 2010-01-22 2011-07-27 徐同德 一种利用喷射器的低压太阳能海水淡化装置
CN101980157B (zh) * 2010-10-13 2014-09-10 中兴通讯股份有限公司 移动终端开机启动方法及移动终端
CN102184110B (zh) * 2011-04-15 2014-03-05 中国联合网络通信集团有限公司 Sd智能卡的识别与驱动加载方法及系统
CN102945176B (zh) * 2012-11-09 2016-09-28 青岛海信移动通信技术股份有限公司 终端设备开机、升级方法和设备
US9672026B2 (en) * 2014-07-21 2017-06-06 Xiaomi Inc. Light app offline updating method, device and terminal
CN104506902B (zh) * 2014-12-05 2018-11-06 惠州Tcl移动通信有限公司 一种器件兼容的方法、装置及移动终端
JP6447297B2 (ja) * 2015-03-26 2019-01-09 富士通株式会社 通信方法、情報処理装置、及びプログラム
CN104778135B (zh) * 2015-04-15 2018-04-27 上海与德通讯技术有限公司 一种器件兼容方法及系统
CN105139641B (zh) * 2015-09-29 2017-11-24 滴滴（中国）科技有限公司 一种基于WiFi中继站的车辆调度方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1979416A (zh) * 2005-12-09 2007-06-13 英业达股份有限公司 驱动程序加载系统及方法
CN102510531A (zh) * 2011-10-20 2012-06-20 山东泰信电子有限公司 一种自动识别数字电视机顶盒调谐器和解调器的方法
CN103942078A (zh) * 2014-04-30 2014-07-23 华为技术有限公司 一种加载驱动程序的方法及嵌入式设备
CN104932918A (zh) * 2015-06-02 2015-09-23 惠州Tcl移动通信有限公司 移动终端及其lcd驱动程序的加载方法
CN107145363A (zh) * 2017-03-21 2017-09-08 捷开通讯(深圳)有限公司 一种终端开机过程的驱动程序加载方法及终端设备

Also Published As

Publication number Publication date
US10871972B2 (en) 2020-12-22
CN107145363A (zh) 2017-09-08
US20200012502A1 (en) 2020-01-09

Similar Documents

Publication Publication Date Title
WO2018171570A1 (zh) 一种终端开机过程的驱动程序加载方法及终端设备
WO2013133530A1 (en) Electronic device to restore mbr, method thereof, and computer-readable medium
WO2020085636A1 (en) Electronic device for displaying list of executable applications on split screen and operating method thereof
WO2020119559A1 (zh) 显示面板的驱动架构及方法
WO2019039809A1 (en) METHOD AND ELECTRONIC DEVICE FOR SWITCHING THE OPERATING MODE OF A DISPLAY
WO2017088549A1 (zh) 一种预留智能终端电池电量的实现方法及系统
WO2014189275A1 (en) Apparatus and method of recognizing external device in a communication system
WO2020155537A1 (zh) 一种待机模式切换方法、装置、电子设备及存储介质
WO2018171534A1 (zh) 基于移动终端的双摄像头供电控制方法、系统及移动终端
WO2016123898A1 (zh) 一种短信管理方法及其移动终端
WO2019098696A1 (en) Display device and method for controlling independently by a group of pixels
WO2020135049A1 (zh) 显示面板的过流保护方法及显示装置
WO2019100593A1 (zh) 电视待机开机方法、电视及计算机可读存储介质
WO2018035929A1 (zh) 一种验证码的处理方法及装置
WO2019164248A1 (en) Method for adaptively controlling low power display mode and electronic device thereof
WO2018058835A1 (zh) 一种通话模式监控方法、系统及通信终端
WO2018145597A1 (zh) 基于移动终端的屏幕补光拍照方法及系统、移动终端
WO2016086558A1 (zh) 智能终端信息显示方法及智能终端
WO2018186587A1 (ko) 전원 안정화 회로 및 그가 적용된 디스플레이 장치
WO2012163216A1 (zh) 一种针对java程序的移动终端输入控制方法和装置
WO2021017332A1 (zh) 语音控制报错方法、电器及计算机可读存储介质
WO2019041356A1 (zh) 终端断电处理方法、设备及计算机可读存储介质
WO2017206453A1 (zh) 应用图标显示方法及系统
WO2019083283A1 (en) ELECTRONIC IMAGE DISPLAY DEVICE AND ITS CONTROL METHOD
WO2019233092A1 (zh) 历史空气质量显示方法、终端、净化器、系统和介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18770724

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18770724

Country of ref document: EP

Kind code of ref document: A1