Advanced graphics driver architecture supporting multiple system emulations

TLDR: In this article, the authors propose a support architecture for display device drivers containing a minimum of hardware-specific software code, which can support only a relatively few common functions, which act as building blocks for the larger, more complex operations typically requested by graphics engines.

Abstract: Disclosed is a support architecture that facilitates use of display device drivers containing a minimum of hardware-specific software code. A driver need support only a relatively few common functions, which act as building blocks for the larger, more complex operations typically requested by graphics engines. In order to mediate between the limited-instruction-set device driver and the various higher-level graphics engines, the invention includes a series of translation modules that simplify engine-originated instructions into simpler graphic components. A video manager supervises routing of instructions to the specific drivers they designate, and serializes access to hardware components so that graphic commands execute atomically (i.e., without interruption). The invention can accommodate multiple device drivers in parallel or serial configurations. Device drivers may be paired with specific graphics adapters, or multiple drivers, each responsive to a different graphics engine, can share a single graphics adapter. A particular driver may be selected by an application program, by a graphics engine, by a translation module, or by the video manager based on considerations of compatibility and efficiency. Ordinarily, a device driver controls the entire video display or a discrete region thereof during the time it processes a particular graphic function; however, the invention can also accommodate multiple video displays, each controlled by a separate device driver.