Display Drivers and the Run-Time Image (Windows CE 5.0)
The emulated blit functions are located in a library named Emul.lib. The display driver links to this library through a link directive during the driver's Sysgen build phase. The GPE library is provided in binary form and links to the driver during the Sysgen build phase.
The ROM Image Builder tool (Romimage.exe) creates run-time images. For most sample display drivers, the Common.bib file directs Romimage.exe to include the appropriate driver in the run-time image, based on the display environment variables selected. The Common.bib file is in the %_WINCEROOT%\Public\Common\OAK\Files directory.
Each sample display driver is associated with an environment variable of the form BSP_DISPLAY_NAME, for example, or BSP_DISPLAY_RAGEXL.
For each variable set, the associated driver and driver registry information is included in the run-time image.
Multiple display drivers can be included in the run-time image. If so, the correct driver is loaded based on the hardware detected and the PCI template information in the registry. Platform.reg files and the Common.reg files contain example registry settings for many display drivers.
If the display controller found by the PCI bus driver matches the PCI configuration information specified, the driver instance tree is populated with instance information for this card.
When GWES starts, it enumerates the display candidate's list, which contains instance information, by looking for a specific driver to load for that device. If it cannot find a driver with a specific name, it loads the default driver, Ddi.dll.
See Also
Loading Device Drivers | PCI Bus Driver | Run-Time Image Build Process | Display Driver Development Concepts | Display Driver Extensions | Display Driver Samples
Send Feedback on this topic to the authors