W_RECONFIGURE_HANDLER callback function

Note   NDIS 5. x has been deprecated and is superseded by NDIS 6. x. For new NDIS driver development, see Network Drivers Starting with Windows Vista. For information about porting NDIS 5. x drivers to NDIS 6. x, see Porting NDIS 5.x Drivers to NDIS 6.0.

MiniportReconfigure is a function that the NDIS library currently never calls but that a MiniportInitialize function can call as an internal driver function.

Syntax

W_RECONFIGURE_HANDLER MiniportReconfigure;

NDIS_STATUS MiniportReconfigure(
  _Out_ PNDIS_STATUS OpenErrorStatus,
  _In_  NDIS_HANDLE  MiniportAdapterContext,
  _In_  NDIS_HANDLE  WrapperConfigurationContext
)
{ ... }

Parameters

• OpenErrorStatus [out]
  Pointer to a variable that MiniportReconfigure sets to an NDIS_STATUS_XXX code specifying additional information about the error if MiniportReconfigure will return NDIS_STATUS_OPEN_ERROR.

• MiniportAdapterContext [in]
  Specifies the handle to a miniport driver-allocated context area in which the driver maintains per-NIC state, set up by MiniportInitialize with NdisMSetAttributes or NdisMSetAttributesEx.

• WrapperConfigurationContext [in]
  Specifies a handle used only during initialization for calls to NdisXxx configuration and initialization functions. For example, this handle is a required parameter to NdisOpenConfiguration and the NdisImmediateReadXxx and NdisImmediateWriteXxx functions.

Return value

MiniportReconfigure either returns NDIS_STATUS_SUCCESS or it can return any driver-determined value, such as one of the following:

NDIS_STATUS_NOT_ACCEPTED

NDIS_STATUS_OPEN_ERROR

NDIS_STATUS_FAILURE

Remarks

As an internal driver function, MiniportReconfigure might be called from MiniportInitialize to reconfigure a NIC to new parameters returned by one of the NdisXxx bus-relative configuration functions. For example, a MiniportReconfigure function might be used to support Plug and Play NICs or software-configurable NICs.

Because an internal MiniportReconfigure function is called from MiniportInitialize, no other driver request can be outstanding when MiniportReconfigure is called, and NDIS will never submit another request to the miniport driver until its caller, MiniportInitialize, returns control.

Like MiniportInitialize, MiniportReconfigure can be preempted by an interrupt if the driver has already called NdisMRegisterInterrupt or if the NIC shares an IRQ.

As an internal driver function called from MiniportInitialize, MiniportReconfigure can be pageable code.

Requirements

See also

MiniportInitialize

Send comments about this topic to Microsoft