DriverEntry of Video Miniport Driver
ULONG DriverEntry(
IN PVOID Context1, | |
IN PVOID Context2 | |
); |
Each miniport driver must have a function explicitly named DriverEntry in order to be loaded.
Parameters
Context1
Points to a context with which the miniport driver must call VideoPortInitialize.
Context2
Points to a second context with which the miniport driver must call VideoPortInitialize.
Return Value
DriverEntry returns the value returned by VideoPortInitialize.
Comments
DriverEntry is called directly by the I/O system.
First, DriverEntry allocates memory on the stack and calls VideoPortZeroMemory to initialize a VIDEO_HW_INITIALIZATION_DATA structure. Then, DriverEntry fills in driver-supplied data in the VIDEO_HW_INITIALIZATION_DATA structure and calls VideoPortInitialize.
If a miniport driver supports adapter(s) that can be connected on different types of I/O bus, such as both MicroChannel and Isa type buses, it should call VideoPortInitialize once for each type of I/O bus. Such a miniport driver must return the lowest value returned by its calls to VideoPortInitialize from the DriverEntry function. The writer of such a driver should make no assumptions about the values returned by VideoPortInitialize.
See Also
HwVidFindAdapter, VIDEO_HW_INITIALIZATION_DATA, VideoPortInitialize, VideoPortZeroMemory