Display Driver Samples
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
Sample code for the sample drivers is in %_WINCEROOT%\Public\Common\OAK\Drivers\Display. For the sample display drivers, software acceleration is provided through emulation libraries, and hardware acceleration is limited to two-dimensional graphics operations.
These samples include:
- ATI Sample Display Driver
- FLAT Sample Display Driver
- Sample Blit Acceleration
- Sample DrvEscape Function
The following table shows files to help you work with monolithic and GPE-based display drivers.
| File | Description |
|---|---|
Winddi.h |
Contains the core definitions for display and printer device drivers. Use this file if you are creating a monolithic driver because it describes the entry points, data types, and symbolic constants you need to receive and process drawing requests from GWES. This file also contains important definitions for you, if you are using GPE. Many GWES data structures propagate through the GPE layer into the GPE objects. |
Emul.h |
Describes the set of raster drawing helpers inside the raster emulation library. Creating fast raster output is very important, because more than 95 percent of the pixels on a display screen are drawn using raster drawing calls. The emulation library provides a reasonably good solution for drawing raster data in software. However, if your display device can perform drawing using accelerated hardware, consider using the hardware in place of the raster emulation library. |
GPE.h |
Contains the basic set of data structures and symbol definitions you need to use the GPE library. |
GPE source files |
Contains GPE source files. Located in %_WINCEROOT%\Public\Common\OAK\Drivers\Display. |
The following table shows the features supported by the ATI and MQ200 display drivers.
| Element | ATI | MQ200 |
|---|---|---|
Driver name |
Ddi_ragexl.dll |
Ddi_mq200.dll |
Environment variable |
BSP_DISPLAY_RAGEXL |
BSP_DISPLAY_MQ200 |
Path to source code |
%_WINCEROOT%\Public\Common\OAK\Drivers\Display\ATI |
%_WINCEROOT%\Public\Common\OAK\Drivers\Display\MQ200 |
Color support |
Yes |
Yes |
Bit depths |
16 bpp |
16 bpp |
Display resolution |
640x480 720x480 800x600 1024x768 1280x1024 |
640x480 800x600 1024x768 1152x864 1280x1024 |
Software acceleration |
Yes |
Yes |
Hardware acceleration |
Yes |
Yes |
Line routines |
Software and hardware |
Software and hardware |
Blit routines |
Software and hardware |
Software and hardware |
Mouse cursor |
Hardware |
Hardware |
Antialiased text support |
Yes |
Yes |
Dirty rectangle driver |
No |
No |
Hardware platform restrictions |
|
|
The following table shows the features supported by the VGA flat and VGA rotation-enabled.
| Element | VGA flat | VGA RFLAT |
|---|---|---|
Driver name |
Ddi_flat.dll |
Ddi_rflat.dll |
Environment variable |
BSP_DISPLAY_FLAT |
BSP_DISPLAY_FLAT |
Path to source code |
%_WINCEROOT%\Public\Common\OAK\Drivers\Display\VGAFLAT |
%_WINCEROOT%\Public\Common\OAK\Drivers\Display\RFLAT |
Color support |
Yes |
Yes |
Bit depths |
8, 16, 24, & 32 bpp |
8, 16, 24, & 32 bpp |
Display resolution |
No restrictions aside from hardware limits and as supported by VESA BIOS |
No restrictions aside from hardware limits and as supported by VESA BIOS. |
Software acceleration |
Yes |
Yes |
Hardware acceleration |
No |
No |
Line routines |
Software |
Software |
Blit routines |
Software |
Software |
Mouse cursor |
Software |
Software |
Antialiased text support |
Yes |
Yes |
Dirty rectangle driver |
No |
No |
Hardware platform restrictions |
x86 only |
x86 only |
Notes |
Requires VESA BIOS version 2.0 or later. Run Vesatest.exe to verify compatibility and needed modes. |
Requires VESA BIOS version 2.0 or later. Run Vesatest.exe to verify compatibility and needed modes. |
See Also
Concepts
How to Decide Whether to Use GPE in a Display Driver
FLAT Sample Display Driver
ATI Sample Display Driver
ATI Sample Display Driver Optimization
Sample DrvEscape Function
Sample Blit Acceleration
Display Driver Performance Profiling
Display Driver Registry Settings
Display Driver Development Concepts
Display Driver Extensions
Display Driver Recommendations