Table of contents
GDI
TOC
Collapse the table of content
Expand the table of content

Required Graphics Driver Functions

Last Updated: 2/14/2017

All graphics drivers must support the entry points that GDI calls to enable and disable the driver, the PDEV structure, and the surface associated with each PDEV. The following table lists the needed functions in the order in which they are typically called.

Entry PointDescription

DrvEnableDriver

As the initial driver entry point, this function provides GDI with the driver version number and entry points of optional functions supported. This is also the only driver function that GDI calls by name. All of the other driver functions are accessed through a table of function pointers. Unlike DrvEnableDriver, the names of the other driver functions are not fixed.

DrvGetModes

Lists the modes supported by a specified video hardware device. (This function is required of display drivers only.)

DrvEnablePDEV

Enables a PDEV.

DrvCompletePDEV

Informs the driver upon completion of device installation.

DrvEnableSurface

Creates a surface for a specified hardware device.

DrvDisableSurface

Informs the driver that the surface created for the current device is no longer needed.

DrvDisablePDEV

When the hardware is no longer needed, frees memory and resources used by the device and any surface created, but not yet deleted.

DrvDisableDriver

Frees all allocated resources for the driver and returns the device to its initial state.

DrvAssertMode

Resets the video mode for a specified hardware device. (This function is required of display drivers only.)

DrvResetDevice

Resets the device when it has become inoperable or unresponsive.

Send comments about this topic to Microsoft

© 2017 Microsoft