US20030202408A1 - Method and apparatus for updating device driver control data - Google Patents
Method and apparatus for updating device driver control data Download PDFInfo
- Publication number
- US20030202408A1 US20030202408A1 US10/457,392 US45739203A US2003202408A1 US 20030202408 A1 US20030202408 A1 US 20030202408A1 US 45739203 A US45739203 A US 45739203A US 2003202408 A1 US2003202408 A1 US 2003202408A1
- Authority
- US
- United States
- Prior art keywords
- control data
- driver
- driver control
- volatile memory
- supplemental
- 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.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/10—Program control for peripheral devices
- G06F13/102—Program control for peripheral devices where the programme performs an interfacing function, e.g. device driver
-
- 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
Definitions
- Embodiments of the present invention provide a method and apparatus for updating device driver control data. More particularly, embodiments of the present invention provide a method and apparatus for modifying the control data that is used by a device driver in a computer system, or for providing new control data to the device driver.
- a device driver is a program that controls a peripheral device in a computer system.
- An example of a device driver is a video driver, which controls a video device, such as a cathode ray tube (CRT) monitor.
- Other examples of device drivers are a keyboard driver, a mouse driver, or a modem driver.
- device drivers are typically stored on the disk drive.
- Device drivers contain control data that specify parameters which are used by the device driver to control the peripheral.
- the control data for a video driver includes timing or mode data, such as dot clock, control register, and watermark data. Dot clock and control register data specify parameters for the timing of signals that are sent to the video display device, and watermark data specifies parameters for the input bandwidth to the video display device.
- the timing control data for a video device driver may have to be changed when the system configuration changes, such as when a new processor is installed in the system.
- Another example of modifying device driver control data is adding new video driver control data to support a new video display mode that is being added to the system, such as the addition of 1024 bit ⁇ 768 bit ⁇ 16 bit resolution capability, or a new frequency or clocking scheme.
- device driver control data was stored on the same storage medium as the device driver (e.g., a disk memory). In some systems, the control data was hard-coded into the device driver. In other systems, the control data was stored separately on the storage medium. If the device driver control data is stored on a disk memory, for example, then updating the control data requires that the data stored in the disk memory (“the disk image”) be modified. If the driver control data is hard-coded into the driver, then the only practical way to modify the control data is to install a new driver. This can be expensive because drivers are typically as large as one-half a million lines of code, and because different drivers may be produced by different manufactures.
- FIG. 1 is a block diagram of a computer system which contains a device driver having control data that may be updated according to one embodiment of the present invention.
- FIG. 2 is a flow chart of a method of updating control data for a device driver according to one embodiment of the present invention.
- FIG. 3 is a flow chart of a method by which a disk driver may obtain supplemental control data according to one embodiment of the present invention.
- FIG. 4 is a diagram of a device driver supplemental control data table according to one embodiment of the present invention.
- FIG. 1 is a block diagram of a computer system 100 which contains a device driver having control data that may be updated according to one embodiment of the present invention.
- System 100 contains a processor 101 coupled to a chipset 102 .
- the chipset may be coupled to a system memory 103 and a number of peripheral devices such as modem 108 , display 109 , and storage medium 110 .
- the chipset is also coupled to non-volatile memory 120 .
- Processor 101 may be coupled to chipset 102 by one or more busses and may communicate with each other through chipset 102 .
- the term “coupled” is intended to encompass and be broader than the term “directly connected,” and also includes the term “indirectly connected.”
- Processor 101 may be a general purpose microprocessor, such as the Pentium II® processor made by the Intel Corporation®) of Santa Clara, Calif., or may be an application specific processor.
- System memory may be, for example, 64K of DRAM.
- Modem 108 may be connected though a telephone system to a network such as the Internet.
- Display 109 may be a standard computer display device such as a CRT monitor or a liquid crystal diode (LCD) display.
- LCD liquid crystal diode
- Storage medium 110 may be a computer disk driver or other non-volatile memory device and may store an operating system 112 (such as Microsoft (Windows98®), a device driver 114 , and device driver control data update instructions 117 .
- Device driver 114 may be, for example, a video device driver that controls display 109 .
- Device driver 114 could also be, for example, a modem device driver that controls modem 108 .
- Device driver 114 contains device driver control data 115 , which specifies parameters used by device driver 114 to control a peripheral. For example, assuming that device driver 114 is a video device driver, control data 115 may the mode data or timing data used by video device driver 114 to control display 109 .
- control data 115 may be 8 KiloBytes in size.
- storage medium 110 typically stores multiple device drivers.
- storage medium 110 also may store other programs and data.
- Device driver 114 and device driver control data update instructions 117 may or may not be part of the operating system 112 .
- FIG. 1 shows non-volatile memory 120 containing supplemental device driver control data 127 .
- Non-volatile memory 120 may be, for example, a 256 KiloBytes or 1 MegaByte flash memory. In the alterative, non-volatile memory 120 may be on the processor chip or may be a second disk storage device. A person of skill in the art will appreciate that non-volatile memory 120 may be any non-volatile memory device.
- Supplemental device driver control data 127 is used by device driver 114 in addition to, or instead of, some or all of control data 115 .
- Supplemental device driver control data 127 may be organized as a data structure, as discussed below with reference to FIG. 4.
- Supplemental device driver control data 127 may be stored on non-volatile memory 120 as part of a firmware hub.
- supplemental device driver control data 127 may be stored on non-volatile memory 120 as part of Basic Input Output System (BIOS) supplemental data.
- BIOS Basic Input Output System
- Driver control data update instructions 117 are executed by processor 101 to modify or add to the control data used by one or more device drivers. For example, control data update instructions 117 may be performed to update the driver control data used by device driver 114 through a modification of supplemental device driver control data 127 .
- the driver control data update instructions 117 may be implemented, for example, in a high level procedural or object-oriented compiled or interpreted language programming language. However, the programs can be implemented in assembly or machine language.
- FIG. 2 shows a flow chart of a method of updating device driver control data according to one embodiment of the present invention.
- a request to update device driver control data is received ( 201 ), and new device driver control data is received ( 202 ).
- the new device driver control data may be received, for example, through modem 108 over a network such as the Internet.
- new device driver control data may be received over a local area network from a server.
- the new device driver control data may be provided by any other known means.
- the device driver control data update instructions 117 compares the new device driver control data with the supplemental device driver data 127 stored on non-volatile memory 120 to determine if the supplemental device driver data 127 already contains the updated data ( 203 ). If the nonvolatile memory 120 already contains the supplemental data, then it does not need to be updated and the process terminates. If the non-volatile memory 120 does not contain the supplemental data or contains different supplemental data, then the new device driver control data is written ( 204 ) to non-volatile memory 120 .
- the device driver may need to update its control data whenever the device driver is initiated ( 301 ).
- Device driver control data 115 is then read ( 302 ) from the non-volatile memory 120 into the system memory 103 .
- the device driver may determine if the non-volatile memory 120 contains supplemental device driver control data ( 303 ). If the non-volatile memory does not contain supplemental device driver control data, then the control data 115 may be used, and the device driver proceeds to normal operation without updating the driver control data.
- the supplemental device driver control data 127 is read into system memory ( 304 ) and the device driver control data 115 that had been read into system memory is replaced or added to with the supplemental device driver control data ( 305 ).
- the supplemental control data is read by reading the size of the data structure and caching the entire data structure into system memory as a block.
- a checksum for the data structure is verified and a data structure version is read to determine the version of the data structure being used.
- the device driver 114 accesses the supplemental device driver control data 127 indirectly though driver control data update instructions 117 .
- FIG. 4 An embodiment of a device driver supplemental control data structure is shown in FIG. 4.
- the supplemental control data structure 400 shown in FIG. 4 contains a header 410 and three tables 420 , 430 , and 440 .
- the header may contain a signature field 411 , a size field 412 , a checksum field 413 , a version field 414 , and three table offset fields 415 , 416 , and 417 .
- the signature field 411 may be, for example, a string of 8 characters and may be used to identify the supplemental control data table 400 in non-volatile memory device 120 .
- the size field 412 may contain the size of structure 200 (for example, 8 KiloBytes) and may be used by the device driver 114 when reading the device driver supplemental data.
- the checksum 413 may be used to verify the validity of the table 200
- the version 414 may be used to determine which version of the supplemental driver control data structure is being used.
- Each table offset field contains the offset to the address of one of the tables.
- table offset 415 may be the offset to table 420
- table offset 416 may be the offset to table 430
- table offset 417 may be the offset to table 440 .
- Each table may contain: a field for the number of entries; an entry size field; and one or more table entries.
- table 420 may contain a number of entries field 421 that specifies the number n of entries in table 420 , and an entry size field 422 that specifies the size of each entry in table 420 .
- Each table may contain a different type of driver control data.
- Tables 420 , 430 , and 440 may be, for example, a dot clock data table, a control register data table, and a watermark data table. In this example, the number of entries in the dot clock data table typically maybe 50 , and the size of each entry typically may be 25 bytes.
- the driver control data update instructions 117 may add a new table to structure 400 by appending a new table offset to the end of header 410 and by appending the new table itself after the end of the last table. If the structure were as shown in FIG. 4, for example, a new fourth table may be added by appending a table-four offset after the end of header 410 , and by appending the forth table to the end of the third table 440 . Similarly, new entries may be added to any of the tables by increasing the number of entries field and by appending the new entries to the end of the table. In this way, the content of the device driver supplemental data may be easily modified in the future.
- structure 400 is described herein, supplemental device driver data 127 may be stored using other data structures.
- the device driver 114 determines whether an item of supplemental driver control data 127 corresponds to an item of device driver control data 115 that has been read into system memory 103 . If the item of supplemental data corresponds to an item of driver control data in system memory, the device driver replaces the item of driver control data in system memory with the corresponding supplemental driver control data. If the item of supplemental data does not correspond to any item of driver control data is system memory, the device driver adds the item of supplemental driver control data to the driver control data stored in system memory.
- structure 400 contains supplemental control data for a video driver
- the nth entry in each table taken as a set of parameters, may specify a single video driver “mode.”
- An example of a video driver mode might be one that supports 1024 bit ⁇ 768 bit ⁇ 16 bit resolution.
- a video driver mode may be specified, for example, by the 3 rd entry in dot clock data table 420 , the 3 rd entry in control register data table 430 , and the 3 rd entry in watermark data table 440 .
- a new video driver mode may be added in this example by adding a new entry to the dot clock data table 420 , the control register data table 430 , and watermark data table 440 .
- a new mode may be disabled by clearing the entry for that mode in each table.
- Embodiments of the present invention provide device drivers with forward compatibility, and allow for driver control data updates, without modifying the contents of the storage medium that stores the device driver.
- the driver control data update instructions may be stored on a different storage medium that the device driver.
- the steps shown in FIGS. 2 and 3 can be re-ordered where appropriate and one or more of those steps may be executed concurrently or omitted.
- Another example of a modification covered by the above teachings and within the purview of the appended claims is an implementation on computer hardware other than that shown in FIG. 1.
- a data structure other than that shown in FIG. 4 may be used in the invention.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
A method and apparatus for updating control data for a device driver that is stored on a first non-volatile memory. New driver control data is written to a second non-volatile memory.
Description
- Embodiments of the present invention provide a method and apparatus for updating device driver control data. More particularly, embodiments of the present invention provide a method and apparatus for modifying the control data that is used by a device driver in a computer system, or for providing new control data to the device driver.
- A device driver is a program that controls a peripheral device in a computer system. An example of a device driver is a video driver, which controls a video device, such as a cathode ray tube (CRT) monitor. Other examples of device drivers are a keyboard driver, a mouse driver, or a modem driver. In a computer system, device drivers are typically stored on the disk drive. Device drivers contain control data that specify parameters which are used by the device driver to control the peripheral. For example, the control data for a video driver includes timing or mode data, such as dot clock, control register, and watermark data. Dot clock and control register data specify parameters for the timing of signals that are sent to the video display device, and watermark data specifies parameters for the input bandwidth to the video display device.
- It is periodically necessary to modify the control data for a device driver. For example, the timing control data for a video device driver may have to be changed when the system configuration changes, such as when a new processor is installed in the system. In addition, it may be necessary to change the device driver control data to fix a flaw in the system. Another example of modifying device driver control data is adding new video driver control data to support a new video display mode that is being added to the system, such as the addition of 1024 bit×768 bit×16 bit resolution capability, or a new frequency or clocking scheme.
- Previously, device driver control data was stored on the same storage medium as the device driver (e.g., a disk memory). In some systems, the control data was hard-coded into the device driver. In other systems, the control data was stored separately on the storage medium. If the device driver control data is stored on a disk memory, for example, then updating the control data requires that the data stored in the disk memory (“the disk image”) be modified. If the driver control data is hard-coded into the driver, then the only practical way to modify the control data is to install a new driver. This can be expensive because drivers are typically as large as one-half a million lines of code, and because different drivers may be produced by different manufactures. Even if the driver control data is stored separately on the disk memory, it is necessary to perform the sometimes expensive and difficult task of modifying the disk memory. If an organization is operating a network that has hundreds of personal computers, for example, this may require the organization's Information Technology (IT) department to back-up and restore the disk image for each of these computers because the disk memories may contain user data or other software.
- Based on the foregoing, there is a need for a method and apparatus for updating device driver control data without modifying the contents of the storage medium that stores the device driver.
- FIG. 1 is a block diagram of a computer system which contains a device driver having control data that may be updated according to one embodiment of the present invention.
- FIG. 2 is a flow chart of a method of updating control data for a device driver according to one embodiment of the present invention.
- FIG. 3 is a flow chart of a method by which a disk driver may obtain supplemental control data according to one embodiment of the present invention.
- FIG. 4 is a diagram of a device driver supplemental control data table according to one embodiment of the present invention.
- Embodiments of the present invention provide a method and apparatus for updating device driver control data without modifying the contents of the storage medium that stores the device driver. FIG. 1 is a block diagram of a
computer system 100 which contains a device driver having control data that may be updated according to one embodiment of the present invention.System 100 contains aprocessor 101 coupled to achipset 102. The chipset may be coupled to asystem memory 103 and a number of peripheral devices such asmodem 108,display 109, andstorage medium 110. The chipset is also coupled to non-volatile memory 120.Processor 101,system memory 103,modem 108,display 109, andstorage medium 110 maybe coupled tochipset 102 by one or more busses and may communicate with each other throughchipset 102. The term “coupled” is intended to encompass and be broader than the term “directly connected,” and also includes the term “indirectly connected.”Processor 101 may be a general purpose microprocessor, such as the Pentium II® processor made by the Intel Corporation®) of Santa Clara, Calif., or may be an application specific processor. System memory may be, for example, 64K of DRAM.Modem 108 may be connected though a telephone system to a network such as the Internet.Display 109 may be a standard computer display device such as a CRT monitor or a liquid crystal diode (LCD) display. -
Storage medium 110 may be a computer disk driver or other non-volatile memory device and may store an operating system 112 (such as Microsoft (Windows98®), adevice driver 114, and device driver controldata update instructions 117.Device driver 114 may be, for example, a video device driver that controls display 109.Device driver 114 could also be, for example, a modem device driver that controlsmodem 108.Device driver 114 contains devicedriver control data 115, which specifies parameters used bydevice driver 114 to control a peripheral. For example, assuming thatdevice driver 114 is a video device driver,control data 115 may the mode data or timing data used byvideo device driver 114 to controldisplay 109. In this example,control data 115 may be 8 KiloBytes in size. Although only onedevice driver 114 is shown in FIG. 1,storage medium 110 typically stores multiple device drivers. In addition,storage medium 110 also may store other programs and data.Device driver 114 and device driver controldata update instructions 117 may or may not be part of theoperating system 112. - FIG. 1 shows non-volatile memory120 containing supplemental device
driver control data 127. Non-volatile memory 120 may be, for example, a 256 KiloBytes or 1 MegaByte flash memory. In the alterative, non-volatile memory 120 may be on the processor chip or may be a second disk storage device. A person of skill in the art will appreciate that non-volatile memory 120 may be any non-volatile memory device. - In one embodiment, supplemental device
driver control data 127 is used bydevice driver 114 in addition to, or instead of, some or all ofcontrol data 115. Supplemental devicedriver control data 127 may be organized as a data structure, as discussed below with reference to FIG. 4. Supplemental devicedriver control data 127 may be stored on non-volatile memory 120 as part of a firmware hub. In a further embodiment, supplemental devicedriver control data 127 may be stored on non-volatile memory 120 as part of Basic Input Output System (BIOS) supplemental data. - Driver control
data update instructions 117 are executed byprocessor 101 to modify or add to the control data used by one or more device drivers. For example, controldata update instructions 117 may be performed to update the driver control data used bydevice driver 114 through a modification of supplemental devicedriver control data 127. The driver controldata update instructions 117 may be implemented, for example, in a high level procedural or object-oriented compiled or interpreted language programming language. However, the programs can be implemented in assembly or machine language. - FIG. 2 shows a flow chart of a method of updating device driver control data according to one embodiment of the present invention. A request to update device driver control data is received (201), and new device driver control data is received (202). The new device driver control data may be received, for example, through
modem 108 over a network such as the Internet. In another embodiment, new device driver control data may be received over a local area network from a server. A person of ordinary skill in the art would appreciate that the new device driver control data may be provided by any other known means. In one embodiment, the device driver control data updateinstructions 117 compares the new device driver control data with the supplementaldevice driver data 127 stored on non-volatile memory 120 to determine if the supplementaldevice driver data 127 already contains the updated data (203). If the nonvolatile memory 120 already contains the supplemental data, then it does not need to be updated and the process terminates. If the non-volatile memory 120 does not contain the supplemental data or contains different supplemental data, then the new device driver control data is written (204) to non-volatile memory 120. - One method by which the device driver obtains supplemental device driver control data is shown in FIG. 3. According to one embodiment, the device driver may need to update its control data whenever the device driver is initiated (301). Device
driver control data 115 is then read (302) from the non-volatile memory 120 into thesystem memory 103. The device driver may determine if the non-volatile memory 120 contains supplemental device driver control data (303). If the non-volatile memory does not contain supplemental device driver control data, then thecontrol data 115 may be used, and the device driver proceeds to normal operation without updating the driver control data. If the non-volatile memory does contain supplemental devicedriver control data 127, then the supplemental devicedriver control data 127 is read into system memory (304) and the devicedriver control data 115 that had been read into system memory is replaced or added to with the supplemental device driver control data (305). According to one embodiment, the supplemental control data is read by reading the size of the data structure and caching the entire data structure into system memory as a block. In a further embodiment, prior to using the supplemental control data, a checksum for the data structure is verified and a data structure version is read to determine the version of the data structure being used. In another embodiment, thedevice driver 114 accesses the supplemental devicedriver control data 127 indirectly though driver control data updateinstructions 117. - An embodiment of a device driver supplemental control data structure is shown in FIG. 4. The supplemental
control data structure 400 shown in FIG. 4 contains aheader 410 and three tables 420, 430, and 440. The header may contain asignature field 411, asize field 412, achecksum field 413, aversion field 414, and three table offsetfields signature field 411 may be, for example, a string of 8 characters and may be used to identify the supplemental control data table 400 in non-volatile memory device 120. Thesize field 412 may contain the size of structure 200 (for example, 8 KiloBytes) and may be used by thedevice driver 114 when reading the device driver supplemental data. Thechecksum 413 may be used to verify the validity of the table 200, and theversion 414 may be used to determine which version of the supplemental driver control data structure is being used. Each table offset field contains the offset to the address of one of the tables. For example, table offset 415 may be the offset to table 420, table offset 416 may be the offset to table 430, and table offset 417 may be the offset to table 440. - Each table may contain: a field for the number of entries; an entry size field; and one or more table entries. For example, table420 may contain a number of entries field 421 that specifies the number n of entries in table 420, and an
entry size field 422 that specifies the size of each entry in table 420. Each table may contain a different type of driver control data. Tables 420, 430, and 440 may be, for example, a dot clock data table, a control register data table, and a watermark data table. In this example, the number of entries in the dot clock data table typically maybe 50, and the size of each entry typically may be 25 bytes. - The driver control data update
instructions 117 may add a new table to structure 400 by appending a new table offset to the end ofheader 410 and by appending the new table itself after the end of the last table. If the structure were as shown in FIG. 4, for example, a new fourth table may be added by appending a table-four offset after the end ofheader 410, and by appending the forth table to the end of the third table 440. Similarly, new entries may be added to any of the tables by increasing the number of entries field and by appending the new entries to the end of the table. In this way, the content of the device driver supplemental data may be easily modified in the future. Althoughstructure 400 is described herein, supplementaldevice driver data 127 may be stored using other data structures. - In one embodiment, the
device driver 114 determines whether an item of supplementaldriver control data 127 corresponds to an item of devicedriver control data 115 that has been read intosystem memory 103. If the item of supplemental data corresponds to an item of driver control data in system memory, the device driver replaces the item of driver control data in system memory with the corresponding supplemental driver control data. If the item of supplemental data does not correspond to any item of driver control data is system memory, the device driver adds the item of supplemental driver control data to the driver control data stored in system memory. - If, as in the example above,
structure 400 contains supplemental control data for a video driver, then the nth entry in each table, taken as a set of parameters, may specify a single video driver “mode.” An example of a video driver mode might be one that supports 1024 bit×768 bit×16 bit resolution. A video driver mode may be specified, for example, by the 3rd entry in dot clock data table 420, the 3rd entry in control register data table 430, and the 3rd entry in watermark data table 440. A new video driver mode may be added in this example by adding a new entry to the dot clock data table 420, the control register data table 430, and watermark data table 440. In addition, a new mode may be disabled by clearing the entry for that mode in each table. - Embodiments of the present invention provide device drivers with forward compatibility, and allow for driver control data updates, without modifying the contents of the storage medium that stores the device driver. Although several embodiments of the present invention are specifically illustrated and/or described herein, it will be appreciated that modifications and variations of the present invention are covered by the above teachings and within the purview of the appended claims without departing from the spirit and intended scope of the invention. The driver control data update instructions may be stored on a different storage medium that the device driver. As a further example, the steps shown in FIGS. 2 and 3 can be re-ordered where appropriate and one or more of those steps may be executed concurrently or omitted. Another example of a modification covered by the above teachings and within the purview of the appended claims is an implementation on computer hardware other than that shown in FIG. 1. In addition, a data structure other than that shown in FIG. 4 may be used in the invention.
Claims (28)
1. A method of updating control data for a device driver that is stored on a first nonvolatile memory, comprising writing new driver control data to a second nonvolatile memory.
2. The method of claim 1 , wherein the device driver is a video driver and the control data is video driver mode data.
3. The method of claim 2 , wherein the driver control data is stored on the second non-volatile memory in a structure that comprises one or more tables, wherein the tables have n entries, and wherein a video driver mode is specified by a set of parameters comprising of the nth entry in each of the tables.
4. The method of claim 3 , wherein a new type of video driver control data may be provided by adding a new table to the structure, and wherein a new video driver mode may be added by adding a new entry to each of the tables.
5. A method of updating device driver control data for a computer system having a non-volatile disk storage device and a second non-volatile memory, comprising:
storing new device driver control data in the second non-volatile memory without modifying data stored in the non-volatile disk storage device.
6. The method of claim 5 , wherein a new device driver mode may be provided by storing a set of mode parameters in the second non-volatile memory.
7. An apparatus for updating the driver control data for a device driver that is stored in a first non-volatile memory, the apparatus comprising:
a first non-volatile memory to store a device driver;
a processor which executes instructions to perform storing new driver control data on a second non-volatile memory.
8. The apparatus of claim 7 , wherein the device driver is a video driver and the control data is video driver mode data.
9. The apparatus of claim 7 , wherein the second non-volatile memory is a flash memory.
10. A method of obtaining supplemental device driver control data for a device driver stored in a first non-volatile memory, comprising:
reading a set of driver control data from the first non-volatile memory into a system memory;
reading supplemental driver control data from a second non-volatile memory; and
updating the set of driver control data in the system memory based on the supplemental driver control data.
11. The method of claim 10 , wherein the device driver is a video device driver.
12. The method of claim 11 , wherein the driver control data comprises at least one of dot clock, control register, and watermark data.
13. The method of claim 10 , wherein the first non-volatile memory is a disk memory and the second non-volatile memory is a flash memory.
14. The method of claim 10 , wherein updating the set of driver control data in system memory comprises:
determining whether an item of supplemental driver control data corresponds to an item of driver control data in system memory;
if the item of supplemental data corresponds to an item of driver control data in system memory, replacing the item of driver control data in system memory with the corresponding supplemental driver control data; and
if the item of supplemental data does not correspond to any item of driver control data in system memory, adding the item of supplemental driver control data to the set of driver control data in system memory.
15. The method of claim 10 , wherein the method of obtaining device driver supplemental control data is performed each time that the device driver is initiated.
16. The method of claim 10 , further comprising:
determining if the second non-volatile memory contains supplemental driver control data; and
using the set of driver control data read from the first non-volatile memory as the driver control data if the second non-volatile memory does not contain supplemental driver control data.
17. The method of claim 10 , wherein the supplemental driver control data is stored on the second non-volatile memory in a structure comprising one or more tables, wherein the tables have n entries, and wherein a mode is specified by a set parameters comprising the nth entry in each of the tables.
18. A computer system, comprising:
a central processing unit;
a system memory;
a first non-volatile memory which stores a device driver; and
a second non-volatile memory which stores device driver control data.
19. The computer system of claim 18 , wherein the computer system further comprises a display device, and wherein the device driver is a video driver.
20. The computer system of claim 19 , wherein the first non-volatile memory is a disk memory and the second non-volatile memory is a flash memory.
21. A computer-readable medium having stored thereon a device driver and instructions adapted to be executed by a processor, the instructions which, when executed, cause the processor to update the control data for the device driver by:
reading a set of driver control data from a first non-volatile memory into a system memory;
reading supplemental driver control data from a second non-volatile memory; and
updating the set of driver control data in the system memory based on the supplemental driver control data.
22. The computer-readable medium of claim 21 , wherein the device driver is a video device driver.
23. The computer-readable medium of claim 21 , wherein the driver control data comprises at least one of dot clock, control register, and watermark data.
24. The computer-readable medium of claim 21 , wherein the first non-volatile memory is a disk memory and the second non-volatile memory is a flash memory.
25. The computer-readable medium of claim 21 , wherein updating the driver control data in system memory comprises:
determining whether an item of supplemental driver control data corresponds to an item of driver control data in system memory;
if the item of supplemental data corresponds to an item of driver control data in system memory, replacing the item of driver control data in system memory with the corresponding supplemental driver control data; and
if the item of supplemental data does not correspond to any item of driver control data is system memory, adding the item of supplemental driver control data to the set of driver control data in system memory.
26. The computer readable medium of claim 21 , wherein the updating the control data is performed each time that the device driver is initiated.
27. The computer readable medium of claim 21 , wherein the instructions further cause the processor further to update the control data for the device driver by:
determining if the second non-volatile memory contains supplemental driver control data; and
using the set of driver control data from the first non-volatile memory as the driver control data if the second non-volatile memory does not contain supplemental driver control data.
28. The computer readable medium of claim 21 , wherein the supplemental driver control data is stored on the second non-volatile memory in a structure comprising tables, wherein the tables have n entries, and wherein a mode is specified by a set of parameters comprising the nth entry in each of the tables.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/457,392 US20030202408A1 (en) | 2000-02-14 | 2003-06-10 | Method and apparatus for updating device driver control data |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/503,206 US6615286B1 (en) | 2000-02-14 | 2000-02-14 | Method and apparatus for updating device driver control data |
US10/457,392 US20030202408A1 (en) | 2000-02-14 | 2003-06-10 | Method and apparatus for updating device driver control data |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/503,206 Continuation US6615286B1 (en) | 2000-02-14 | 2000-02-14 | Method and apparatus for updating device driver control data |
Publications (1)
Publication Number | Publication Date |
---|---|
US20030202408A1 true US20030202408A1 (en) | 2003-10-30 |
Family
ID=27766361
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/503,206 Expired - Fee Related US6615286B1 (en) | 2000-02-14 | 2000-02-14 | Method and apparatus for updating device driver control data |
US10/457,392 Abandoned US20030202408A1 (en) | 2000-02-14 | 2003-06-10 | Method and apparatus for updating device driver control data |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/503,206 Expired - Fee Related US6615286B1 (en) | 2000-02-14 | 2000-02-14 | Method and apparatus for updating device driver control data |
Country Status (1)
Country | Link |
---|---|
US (2) | US6615286B1 (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070185966A1 (en) * | 2002-11-04 | 2007-08-09 | Alcatel | Device and method for controlling network equipment management data, for a communications network management system |
US20070237141A1 (en) * | 2006-04-05 | 2007-10-11 | Joseph Robert Marchese | Network device detection, identification, and management |
US20080127165A1 (en) * | 2006-11-29 | 2008-05-29 | Sony Ericsson Mobile Communications Ab | System and Method for Updating Device Drivers |
US8584146B1 (en) * | 2012-05-11 | 2013-11-12 | Hobnob, Inc. | Communications driver management |
US8891330B2 (en) | 2008-02-05 | 2014-11-18 | Marvell World Trade Ltd. | Method and apparatus for simultaneously accessing a plurality of memory cells in a memory array to perform a read operation and/or a write operation |
US9374405B2 (en) | 2000-03-14 | 2016-06-21 | Joseph Robert Marchese | Digital video system using networked cameras |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7076536B2 (en) * | 2000-12-21 | 2006-07-11 | Microsoft Corporation | Method and system to access software pertinent to an electronic peripheral device at an address based on a peripheral device identifier |
US7039796B2 (en) * | 2002-06-04 | 2006-05-02 | Hewlett-Packard Development Company, L.P. | Method and system of locating a position in memory at which to store incoming firmware image |
TWI249102B (en) * | 2003-11-07 | 2006-02-11 | Aiptek Int Inc | System and method for automatic installing an application program |
US8266105B2 (en) * | 2006-10-31 | 2012-09-11 | Rebit, Inc. | System for automatically replicating a customer's personalized computer system image on a new computer system |
US20080104146A1 (en) * | 2006-10-31 | 2008-05-01 | Rebit, Inc. | System for automatically shadowing encrypted data and file directory structures for a plurality of network-connected computers using a network-attached memory with single instance storage |
US7870327B1 (en) * | 2007-04-25 | 2011-01-11 | Apple Inc. | Controlling memory operations using a driver and flash memory type tables |
KR102257737B1 (en) * | 2014-08-12 | 2021-05-28 | 삼성전자 주식회사 | Apparatus and method for controlling a throughput in an electronic device |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5357614A (en) * | 1992-09-17 | 1994-10-18 | Rexon/Tecmar, Inc. | Data compression controller |
US5903260A (en) * | 1990-06-18 | 1999-05-11 | Seiko Epson Corporation | Flat device and display driver with on/off power controller used to prevent damage to the LCD |
US5963889A (en) * | 1995-05-23 | 1999-10-05 | Siemens Aktiengesellschaft | Process for the computer-assisted measurement and testing of electric circuits, especially electronic modules, and testing station for implementing the process |
US5964864A (en) * | 1995-04-04 | 1999-10-12 | Ricoh Company | Information processing apparatus for separately processing code information and pattern information |
US6138178A (en) * | 1997-01-29 | 2000-10-24 | Fuji Photo Film Co., Ltd. | Controlled device storing multiple drivers that judges and downloads a particular driver corresponding to a controller's operating system having an identical or greater version number |
US6237019B1 (en) * | 1998-03-18 | 2001-05-22 | International Business Machines Corporation | Method and apparatus for performing a semaphore operation |
US6311232B1 (en) * | 1999-07-29 | 2001-10-30 | Compaq Computer Corporation | Method and apparatus for configuring storage devices |
US6544782B1 (en) * | 2000-11-13 | 2003-04-08 | Synthegen Systems | pREM: a positive selection vector system for direct PCR cloning |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
IT1254937B (en) | 1991-05-06 | 1995-10-11 | DYNAMIC UPDATE OF NON-VOLATILE MEMORY IN A COMPUTER SYSTEM | |
US5644782A (en) * | 1994-10-17 | 1997-07-01 | Motorola, Inc. | System with virtual update capable read-only memory |
US5835594A (en) | 1996-02-09 | 1998-11-10 | Intel Corporation | Methods and apparatus for preventing unauthorized write access to a protected non-volatile storage |
US5930504A (en) | 1996-07-22 | 1999-07-27 | Intel Corporation | Dynamic nonvolatile memory update in a computer system |
-
2000
- 2000-02-14 US US09/503,206 patent/US6615286B1/en not_active Expired - Fee Related
-
2003
- 2003-06-10 US US10/457,392 patent/US20030202408A1/en not_active Abandoned
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5903260A (en) * | 1990-06-18 | 1999-05-11 | Seiko Epson Corporation | Flat device and display driver with on/off power controller used to prevent damage to the LCD |
US5357614A (en) * | 1992-09-17 | 1994-10-18 | Rexon/Tecmar, Inc. | Data compression controller |
US5964864A (en) * | 1995-04-04 | 1999-10-12 | Ricoh Company | Information processing apparatus for separately processing code information and pattern information |
US5963889A (en) * | 1995-05-23 | 1999-10-05 | Siemens Aktiengesellschaft | Process for the computer-assisted measurement and testing of electric circuits, especially electronic modules, and testing station for implementing the process |
US6138178A (en) * | 1997-01-29 | 2000-10-24 | Fuji Photo Film Co., Ltd. | Controlled device storing multiple drivers that judges and downloads a particular driver corresponding to a controller's operating system having an identical or greater version number |
US6237019B1 (en) * | 1998-03-18 | 2001-05-22 | International Business Machines Corporation | Method and apparatus for performing a semaphore operation |
US6311232B1 (en) * | 1999-07-29 | 2001-10-30 | Compaq Computer Corporation | Method and apparatus for configuring storage devices |
US6544782B1 (en) * | 2000-11-13 | 2003-04-08 | Synthegen Systems | pREM: a positive selection vector system for direct PCR cloning |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9374405B2 (en) | 2000-03-14 | 2016-06-21 | Joseph Robert Marchese | Digital video system using networked cameras |
US9979590B2 (en) | 2000-03-14 | 2018-05-22 | Jds Technologies, Inc. | Digital video system using networked cameras |
US20070185966A1 (en) * | 2002-11-04 | 2007-08-09 | Alcatel | Device and method for controlling network equipment management data, for a communications network management system |
US20070237141A1 (en) * | 2006-04-05 | 2007-10-11 | Joseph Robert Marchese | Network device detection, identification, and management |
US9166883B2 (en) * | 2006-04-05 | 2015-10-20 | Joseph Robert Marchese | Network device detection, identification, and management |
US10594563B2 (en) | 2006-04-05 | 2020-03-17 | Joseph Robert Marchese | Network device detection, identification, and management |
US20080127165A1 (en) * | 2006-11-29 | 2008-05-29 | Sony Ericsson Mobile Communications Ab | System and Method for Updating Device Drivers |
US8010959B2 (en) * | 2006-11-29 | 2011-08-30 | Sony Ericsson Mobile Communications Ab | System and method for updating device drivers |
US8891330B2 (en) | 2008-02-05 | 2014-11-18 | Marvell World Trade Ltd. | Method and apparatus for simultaneously accessing a plurality of memory cells in a memory array to perform a read operation and/or a write operation |
US8584146B1 (en) * | 2012-05-11 | 2013-11-12 | Hobnob, Inc. | Communications driver management |
US9134984B2 (en) | 2012-05-11 | 2015-09-15 | Hobnob, Inc. | Virtual network adapter |
Also Published As
Publication number | Publication date |
---|---|
US6615286B1 (en) | 2003-09-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6615286B1 (en) | Method and apparatus for updating device driver control data | |
US7262776B1 (en) | Incremental updating of animated displays using copy-on-write semantics | |
JP2538029B2 (en) | Computer display device | |
US6192375B1 (en) | Method and apparatus for managing files in a storage medium | |
US8549271B1 (en) | Method, system, and computer readable medium for updating and utilizing the contents of a non-essential region of a memory device | |
US7861028B2 (en) | System and method for configuration and management of flash memory | |
US7275135B2 (en) | Hardware updated metadata for non-volatile mass storage cache | |
US20050144609A1 (en) | Methods and apparatus to provide a robust code update | |
US20070130441A1 (en) | Address translation table synchronization | |
US6751658B1 (en) | Providing a reliable operating system for clients of a net-booted environment | |
US5664139A (en) | Method and a computer system for allocating and mapping frame buffers into expanded memory | |
US5987582A (en) | Method of obtaining a buffer contiguous memory and building a page table that is accessible by a peripheral graphics device | |
US6721868B1 (en) | Redirecting memory accesses for headless systems | |
US20040194079A1 (en) | Migration of configuration data from one software installation through an upgrade | |
US20060279578A1 (en) | Systems and methods for updating a frame buffer based on arbitrary graphics calls | |
US20020124142A1 (en) | Compressor stall avoidance mechanism | |
CN1282016A (en) | Display picture during period of leading and turn-off computer | |
US6370633B2 (en) | Converting non-contiguous memory into contiguous memory for a graphics processor | |
US5831639A (en) | Scanning display driver | |
US20060129520A1 (en) | System and method for automatically updating a program in a computer | |
US6980222B2 (en) | Method and apparatus for implementing dynamically sizable color tables | |
US20040123136A1 (en) | Method for modifying executing file on real time and method for managing virus infected file using the same | |
US6654906B1 (en) | Recovery from instruction fetch errors in hypervisor code | |
US7069384B2 (en) | System and method for cache external writing and write shadowing | |
CN107291501A (en) | A kind of system quick start method and electronic equipment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |