Required Graphics Driver Functions
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 Point | Description |
|---|---|
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. |
|
Lists the modes supported by a specified video hardware device. (This function is required of display drivers only.) |
|
Enables a PDEV. |
|
Informs the driver upon completion of device installation. |
|
Creates a surface for a specified hardware device. |
|
Informs the driver that the surface created for the current device is no longer needed. |
|
When the hardware is no longer needed, frees memory and resources used by the device and any surface created, but not yet deleted. |
|
Frees all allocated resources for the driver and returns the device to its initial state. |
|
Resets the video mode for a specified hardware device. (This function is required of display drivers only.) |
|
Resets the device when it has become inoperable or unresponsive. |
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for