For a WDI model, most of the handler parameters are optional. NDIS_MINIPORT_DRIVER_CHARACTERISTICS: This is the original NDIS structure that a Native Wi-Fi miniport uses to register with NDIS.The following are the key parameters of NdisMRegisterWdiMiniportDriver. The one exception is that instead of calling NdisMRegisterMiniportDriver, the IHV miniport calls NdisMRegisterWdiMiniportDriver to tell the operating system to enable the Microsoft WLAN component. The IHV miniport follows most of the guidelines of a regular NDIS miniport's DriverEntry routine. The operating system directly calls the WDI IHV miniport driver's DriverEntry routine. Like existing NDIS drivers, when the IHV driver needs to be loaded to work with the IHV's WLAN adapter, the operating system calls the IHV miniport driver's DriverEntry routine. The INF and install process is similar to that of an IHV Native WLAN miniport driver. There are no changes to the way the WDI IHV miniport driver is loaded and installed on the system.
The mapping of and behavior changes for the NDIS handlers for the Native WLAN IHV miniport when applied to a WDI IHV miniport are described below. The Microsoft WLAN component takes care of the NDIS requirements that are applicable for all Wi-Fi miniports so that every IHV does not have to redo all that work. A Native WLAN Miniport driver’s responsibilities for the NDIS handlers are split between the MS Component and the WDI IHV driver. The WDI IHV miniport is like any other NDIS miniport driver and it would follow the development practices and documentation for any NDIS miniport.
0 kommentar(er)
