Direct3D Mobile Driver Development Concepts
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/28/2008
A Microsoft® Direct3D® Mobile driver provides the actual drawing services that the Direct3D Mobile middleware uses. The middleware is a thin layer of software that handles all call transport, synchronization, and OS integration issues; the driver manages all the memory for display surfaces.
All Direct3D Mobile drivers must implement the functions listed in Direct3D Mobile Driver Functions as callback functions. The Direct3D Mobile driver must specifically export the entry point function D3DM_Initialize using that exact name. You can customize the names of the remaining driver callback functions because those functions are exposed to the Direct3D Mobile middleware through function pointers passed in the call to D3DM_Initialize.
Direct3D Mobile supports only one driver per device.
The following topics provide information on Direct3D Mobile driver development.
- Direct3D Mobile Reference Driver
- Driver Interactions with the Direct3D Mobile Middleware
- Rendering Pipeline in Direct3D Mobile Drivers
- Resources in Direct3D Mobile Drivers
See Also
Other Resources
Direct3D Mobile Display Drivers
Direct3D Mobile Driver Reference