## Display Device Driver Reference for OS/2

[prev][next][parent][TOC]

### Summary and Suggestions

The following is a guideline and list of files, with a brief summary of points as to what functionality, as described previously, is required in each.

vvuser.c

Chip identification, PMI-File processing.

Reserve the address space for mapping into other than A000-BFFF range.

vvstate.c

Chip-specific Restore/UpdateSVGAIOState(), for example, Trident old and new register definitions that cannot be handled by way of PMI entries.

Update memory state. If chip uses enhanced modes, use extended registers to determine if it is in enhanced mode.

Check for greater than 16-color mode determination.

Mode data structure setup, determining the number of horizontal and vertical scanlines and number of colors for current mode.

Video memory state detection, 16-color, 256-color, or other modes.

Restoring I/O state. Check if register ordering is important. Is Sequencer reset required around extended register update?

vvsvga.c

Code routines for getting the register lock state.

Code get and set bank routines.

Ensure vvMaxBanks() routine returns appropriate data for allocating and saving the shadow video buffer.

vvdata.c

Add entries to ahleFgnd, ahlBgnd, apleAll, apleNoTrap.

Add get/set bank routine entries to apfnGetBank and apfnSetBank.

vvmode.c

Cleanups, anything not handled by PMI-File cleandata.

vvpmi.c

Add new token entries for PMI-File parsing.

vvport.c

Install I/O hooks.

vvsvgaio.asm

Routines to be called for new ports hooked in background.

vvsvgaid.asm

Chip Set/Board identification code.

vvdp.h

Create definitions for new adapter type and chip set.

Add function prototypes for new functions defined.