Object oriented device driver system for procedural device drivers

• US 5,727,212 A
• Filed: 04/12/1995
• Issued: 03/10/1998
• Est. Priority Date: 04/12/1995
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Dinallo, Chris A.
• Primary Examiner(s): Oberley, Alvin E.
• Assistant Examiner(s): LAO, SUE X
• Application Number:
  US08/420,919
• Time in Patent Office: 1,063 Days
• Field of Search: 395/700, 395/500, 395/681, 395/680, 395/683
• US Class Current: 719/321
• 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 9/541 via adapters, e.g. between incompatible applications

Abstract

A method of and apparatus for bridging communications between an object oriented component and a procedural programmed device driver are disclosed. Both the object oriented component and the procedural programmed device driver are part of a data processing system. Both the method and apparatus isolate the object oriented component from any device driver, specifically the active device driver, by encapsulating the specific driver information associated with that particular device driver and then transporting requests or commands from the object oriented component to the specific device driver when interfacing with the device driver. The object oriented component generates an interface object that allows for opening communication or closing communication to the device driver as well as initializing the device using the information within the device driver and for controlling the device via the device driver. A transport object is also generated, which allows the transporting of data from the object oriented selected device driver to the object oriented component. This transport object also allows data flow to be controlled between the component and the selected device driver.

Claims

1. An apparatus for bridging communications between an object oriented component and a procedural programmed device driver, which are both part of a data processing system, the apparatus comprising:

an object oriented interface device that couples said object oriented component to said device driver;

means, coupled to said object oriented interface device, for isolating said object oriented component from said device driver, said isolating means including procedural code to open, initialize, control, and close said device driver, and further including first means for providing data flow; and

means for encapsulating device specific information, coupled to said isolating means, said encapsulating means being independent from but responsive to said isolating means, to transport requests and commands to said device driver, and further including second means for providing data flow such that said encapsulating means may communicate with other device drivers besides said device driver.

2. The apparatus according to claim 1, wherein said object oriented interface device further comprises:

means for loading microcode from said object oriented component into said device via said device driver.

3. The method according to claim 1, wherein said isolating means further comprises means for opening communication to said other device drivers.

4. The method according to claim 1, wherein said encapsulating means further comprises means for transporting data from said device driver.

5. In a data processing system having an object oriented component and a plurality of procedural programmed device drivers, a method for bridging communication between said object oriented component and at least one of said plurality of procedural programmed device drivers, comprising the steps of:

isolating said object oriented component from said at least one of said plurality of device drivers using procedural code adapted to open, initialize, control, and close said device drivers;

encapsulating said specific device driver information associated with said at least one of said plurality of device drivers; and

transporting requests or commands, or both from said object oriented component to said at least one of said plurality of device drivers, while providing independent data flow to others of said plurality of device drivers.

6. The method according to claim 5 wherein said step of transporting requests or commands further comprises the steps of:

opening communcation to said at least one of said device drivers; and

initializing said device via said device driver.

7. The method according to claim 6 further comprising the step of:

loading microcode from said object oriented component into said device via said device driver.

8. The method according to claim 6 wherein said transporting step further comprises the step of:

opening communication into other device drivers.

9. The method according to claim 6 wherein said transporting step further comprises the step of transporting data from said device driver.

10. The method according to claim 6 wherein said transporting step further comprises the step of controlling said data flow between said object oriented component and said at least one of said plurality of device drivers.