# US 2010/0169898 A1 · Unified driving method and unified driver apparatus

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2010/0169898 A1
- Document ID: US20100169898A1
- Status: Published application
- Kind: A1
- Application number: 12/650,279
- Filed: 2009-12-30
- Published: 2010-07-01
- Earliest claimed: 2008-12-30
- Assignees: STMicroelectronics R&D (Shanghai) Co. Ltd.
- Inventors: Christophe Quarre; Maoping Weng; Zhe Wu
- Web page: https://patentgrep.com/patent/US20100169898A1

## CPC

- G06F 9/54: Interprogram communication
- G06F 9/44521: {Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The present invention provides a technical solution for a unified driver used in a handheld device. An embodiment of the technical solution may comprise a unified driving method used in a handheld device, which method may comprise: determining driver types of currently installed hardware; setting a current dispatch table on the basis of the driver type and a unified dispatch table suitable for multiple hardware and driving corresponding hardware or software by calling the current dispatch table.

## Claims

### Claim 1

A unified device driving method executed in a handheld electronic device, comprising:
determining a driver type, the driver type representative of a currently available hardware module on the handheld device;
loading, in response to determining said driver type, a plurality of current dispatch table address pointers into a unified dispatch table, the unified dispatch table providing sufficient storage for at least two pointers for each of a plurality of different hardware configurations;
making the current dispatch table address pointers from the unified dispatch table available to a central processing unit; and
driving the currently available hardware module with a plurality of functions, each of the plurality of functions associated with one of the plurality of current dispatch table address pointers loaded in the current dispatch table.

### Claim 2 (depends on 1)

The method according to claim 1, further comprising:
obtaining a plurality of current dispatch table address pointers for a plurality of different hardware configurations supported by said unified device driving method; and
generating said unified dispatch table using said plurality of current dispatch table address pointers.

### Claim 3 (depends on 2)

The method according to claim 2 wherein the obtaining the plurality of current dispatch table address pointers includes obtaining at least two sets of address pointers to functions wherein each set of address pointers represents addresses to functions accessible by each of the plurality of different hardware configurations respectively.

### Claim 4 (depends on 1)

The method according to claim 1 wherein said unified dispatch table is organized according to a function column and an address pointer column, wherein the function column provides for storage of an identifier for each function accessible by each of the plurality of different hardware configurations respectively, and the address pointer column provides for storage of address pointers to objects, the objects implementing said functions.

### Claim 5 (depends on 1)

The method according to claim 1 wherein determining the driver type representative of the currently available hardware module comprises at least one of:
determining that functions performed by the unified device driving method are performed fully in the currently available hardware module;
determining that functions performed by the unified device driving method are performed in a combination of hardware and software; and
determining that functions performed by the unified device driving method are performed fully in software without the participation of hardware.

### Claim 6 (depends on 5)

The method according to claim 5 wherein loading the current dispatch table comprises:
setting a first current dispatch table address pointer to an address of a first function when the first function is executable fully in the currently available hardware module;
setting a second current dispatch table address pointer to an address of a second function when the second function is executable in a combination of the currently available hardware module and software; and
setting a third current dispatch table address pointer to an address of a third function when the third function is executable fully in software.

### Claim 7 (depends on 4)

The method according to claim 4 wherein said unified dispatch table is further organized according to a driver operation column, wherein the driver operation column provides for storage of identifiers indicating driver operations corresponding to all functions supported by the unified driving method such that the plurality of different hardware configurations share corresponding driver operations indicated by the identifiers.

### Claim 8 (depends on 1)

The method according to claim 1 wherein the unified device driving method is a three-dimensional (3D) graphics processing method.

### Claim 9 (depends on 8)

The method according to claim 8 wherein the loading includes:
loading a current dispatch table address pointer to a transform and lighting (TnL) function;
loading a current dispatch table address pointer to a rasterization function; and
loading a current dispatch table address pointer to a back-end processing function.

### Claim 10 (depends on 1)

The method according to claim 1 wherein the determining and the loading includes:
uploading a unified dispatch table from a memory.

### Claim 11

A mobile device, comprising:
a hardware module, the hardware module controllable with software;
a memory having an area for instructions and an area for data structures; and
a central processing unit (CPU) operable to execute instructions stored in the memory area for instructions, the instructions forming a unified driver configured to control the hardware module when the CPU executes the instructions, the control including:
initializing a unified dispatch table configured in the memory area for data structures, the unified dispatch table representing a plurality of columns of function identifiers and a plurality of columns of address pointers;
loading the unified dispatch table with at least one set of function identifiers in the memory area for data structures associated with the columns of function identifiers; and
loading the unified dispatch table with at least one set of address pointers in the memory area for data structures associated with the columns of address pointers, wherein each address in the set of address pointers represents an address of at least one function executable to control the hardware module.

### Claim 12 (depends on 11)

The mobile device according to claim 11, further comprising:
a dispatch manager implemented in a subset of the instructions stored in the memory area for instructions, the dispatch manager having instructions to further control the hardware module when the CPU executes the instructions, the further control including:
accessing the unified dispatch table;
processing requests and directions passed via a unified driver applications programming interface (API);
retrieving information from a software rendering module;
retrieving information from a hardware capabilities module;
passing commands to the software rendering module; and
passing commands to the hardware module.

### Claim 13 (depends on 11)

The mobile device according to claim 11 wherein processing requests and directions includes generating 32-bit commands and passing commands includes passing the 32-bit commands through a command interface.

### Claim 14 (depends on 11)

The mobile device according to claim 11, further comprising:
a dispatch manager implemented in a subset of the instructions stored in the memory area for instructions, the dispatch manager having instructions to further control the hardware module when the CPU executes the instructions, the further control including:
using a function identifier as an index into the unified dispatch table;
retrieving an address pointer from the unified dispatch table; and
retrieving a driver operation indicator from the unified dispatch table.

### Claim 15 (depends on 14)

The mobile device according to claim 14 wherein the further control is further including:
making the address pointer available to the CPU if the driver operation indicator is a fully software driver operation indicator; or
making the address pointer available to the CPU and passing another address pointer to the hardware module if the driver operation indicator is a combination software and hardware driver operation indicator; or
passing the address pointer to the hardware module if the driver operation indicator is a fully hardware driver operation indicator.

### Claim 16 (depends on 11)

The mobile device according to claim 11, further comprising:
a dispatch manager implemented in a subset of the instructions stored in the memory area for instructions, the dispatch manager having instructions to further control the hardware module when the CPU executes the instructions, the further control including:
forming a global rendering context in the memory area for data structures, the global rendering context having pointers into the unified dispatch table; and
passing the global rendering context as an input parameter to each function executable to control the hardware module.

### Claim 17 (depends on 11)

The mobile device according to claim 11 wherein the global rendering context further has pointers to global data structures accessible by the CPU.

### Claim 18 (depends on 11)

The mobile device according to claim 11 wherein the loading includes:
accessing a first current dispatch table associated with a first potential hardware module;
accessing a second current dispatch table associated with a second potential hardware module; and
loading the unified dispatch table with pointers associated with the hardware module in response to accessing the first and second current dispatch tables.

### Claim 19 (depends on 11)

The mobile device according to claim 11 wherein the unified driver is a unified three-dimensional (3D) graphics processing driver.

### Claim 20 (depends on 19)

The mobile device according to claim 19 wherein the unified three-dimensional (3D) graphics processing driver implements an OpenGL/ES protocol.

### Claim 21

A computer-readable medium whose contents configure a mobile device to provide unified driver functionality by performing a method, the method comprising:
initializing a unified dispatch table, the unified dispatch table representing a plurality of columns of function identifiers and a plurality of columns of address pointers;
loading the unified dispatch table with at least one set of function identifiers associated with the columns of function identifiers; and
loading the unified dispatch table with at least one set of address pointers associated with the columns of address pointers, wherein each address in the set of address pointers represents an address of at least one function executable to control the hardware module.
