Storing dynamically loaded device drivers on a mass storage device to support access to removable computer cards

• US 6,081,850 A
• Filed: 02/19/1993
• Issued: 06/27/2000
• Est. Priority Date: 12/27/1991
• Status: Expired due to Term

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Garney, John I.
• Primary Examiner(s): Meky, Moustafa M.
• Application Number:
  US08/019,798
• Time in Patent Office: 2,685 Days
• Field of Search: 395/200, 395/275, 395/375, 395/650, 395/700, 395/500, 364/200, 364/900, 710/1, 710/2, 710/3, 710/8, 710/15, 710/16, 710/17, 710/18, 710/19, 710/62, 710/63
• US Class Current: 710/15
• CPC Class Codes: G06F 12/023 Free address space management
• CPC Class Codes: G06F 13/102 where the programme performs an interfacing function, e.g. device driver G06F13/105 takes precedence; scheduling within device drivers G06F9/52; contention policies within device drivers G06F9/4881
• CPC Class Codes: G06F 13/4068 Electrical coupling
• CPC Class Codes: G06F 9/4415 Self describing peripheral devices

Abstract

Device drivers for removable system resources are stored on a mass storage device to provide dynamic device driver configuration for a computer system. By storing device drivers on a mass storage device, the device drivers need not be stored on their associated feature card and they can be easily updated as changes are required. The computer system comprises a processor, a system memory, a mass storage memory and an interface for receiving removable system resources (generally denoted feature cards or cards). Each feature card has a card information structure (CIS) area. The CIS includes one or more card identification fields that each hold a card identifier. The card identifier is the same for every feature card of a particular type, but it is unique for each different type of feature card. The mass storage device of the computer system has a lookup table which uses the card unique identifiers to map each type of feature card that will be used by the system to an associated device driver for controlling the feature card. Each device driver is stored on the mass storage device. The device driver for a particular feature card is copied into computer system memory upon insertion of the feature card into the computer system. The device driver may then be activated by the processor.

Claims

1. In a computer system having a processor, a system memory, a mass storage memory device and an interface for receiving a removable system resource, a process for dynamically configuring device drivers of removable computer system resources, said process comprising the steps of:

configuring the system memory in a bootstrap initialization; and

after said bootstrap initialization while an application program is running and prior to any subsequent bootstrap initialization, performing the following steps,

(a) receiving a removable system resource at the interface;

(b) retrieving a device driver identifier from the removable system resource;

(c) copying a device driver corresponding to said device driver identifier from the mass storage memory device to the system memory; and

(d) executing said device driver from the system memory.

2. The process as set forth in claim 1 wherein said mass storage memory device further includes a device driver information block (DDIB) header corresponding to said device driver identifier, said copying step further including the step of copying said DDIB header into the system memory.

3. The process as set forth in claim 1 further including the steps of:

storing said device driver on the mass storage memory device in a location corresponding to said device driver identifier; and

updating a device driver lookup table such that, based on said device driver identifier, said device driver lookup table points to a location corresponding to said device driver stored on said mass storage memory device.

4. The process as set forth in claim 1 further including the step of displaying a message indicating that a removable system resource has been received at said interface.

5. The process as set forth in claim 1 further including the step of suspending execution of said application program while said steps of retrieving, copying, and executing are performed.

6. The process as set forth in claim 1 further including the step of retaining said device driver in system memory as long as the removable system resource is coupled to said interface.

7. The process as set forth in claim 1 further including the steps of:

receiving an indication if the removable system resource has been decoupled from the interface; and

disabling access to said device driver.

8. The process as set forth in claim 1 wherein said configuring the system memory step occurs prior to bootstrap initialization.

9. The process as set forth in claim 1 wherein said configuring the system memory step occurs subsequent to bootstrap initialization.

10. The process as set forth in claim 1 further including a step of providing a resource memory in said removable system resource, said resource memory containing said device driver identifier.

11. In a computer system having a processor, a system memory, a mass storage memory device and an interface for receiving a removable system resource, an apparatus for dynamically configuring device drivers of removable computer system resources, said apparatus comprising:

(a) means for configuring the system memory in a bootstrap initialization;

(b) means for receiving a removable system resource at the interface;

(c) means for retrieving a device driver identifier from the removable system resource;

(d) means for copying a device driver corresponding to said device driver identifier from the mass storage memory device to the system memory; and

(e) means for executing said device driver from the system memory, said elements (b) through (e) being operable after said bootstrap initialization while an application program is running and prior to any subsequent bootstrap initialization.

12. The apparatus as set forth in claim 11 wherein said mass storage memory device further includes a device driver information block (DDIB) header corresponding to said device driver identifier, said means for copying further including means for copying said DDIB header into the system memory.

13. The apparatus as set forth in claim 11 further including:

means for storing said device driver on the mass storage memory device in a location corresponding to said device driver identifier; and

means for updating a device driver lookup table such that, based on said device driver identifier, said device driver lookup table points to a location corresponding to said device driver stored on said mass storage memory device.

14. The apparatus as set forth in claim 11 further including means for displaying a message indicating that a removable system resource has been received at said interface.

15. The apparatus as set forth in claim 11 further including means for suspending execution of said application program while said means for retrieving, said means for copying, and said means for executing are operating.

16. The apparatus as set forth in claim 11 further including means for retaining said device driver in system memory as long as the removable system resource is coupled to said interface.

17. The apparatus as set forth in claim 11 further including:

means for receiving an indication if the removable system resource has been decoupled from the interface; and

means for disabling access to said device driver.

18. The apparatus as set forth in claim 11 wherein said means for configuring the system memory is operable prior to bootstrap initialization.

19. The apparatus as set forth in claim 11 wherein said means for configuring the system memory is operable subsequent to bootstrap initialization.

20. The apparatus as set forth in claim 11 further including a resource memory in said removable system resource, said resource memory containing said device driver identifier.