Partager via

MiniportReconfigure (Compact 2013)

  • Article

3/26/2014

Although the NDIS library currently never calls this function, a MiniportInitialize function can call it as an internal driver function.

Syntax

NDIS_STATUS MiniportReconfigure(
  PNDIS_STATUS OpenErrorStatus,
  NDIS_HANDLE MiniportAdapterContext,
  NDIS_HANDLE WrapperConfigurationContext
);

Parameters

  • OpenErrorStatus
    [out] Points 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-allocated context area in which the driver maintains per-network adapter state, set up by MiniportInitialize with NdisMSetAttributes or NdisMSetAttributesEx.
  • WrapperConfigurationContext
    [in] Specifies a handle that is used only during initialization for calls to NdisXXX configuration and initialization functions. For example, this handle is a required parameter to NdisOpenConfiguration.

Return Value

The following table shows the status values that MiniportReconfigure returns

Value

Description

NDIS_STATUS_SUCCESS

The miniport was successfully reconfigured.

NDIS_STATUS_NOT_ACCEPTED

This value usually is a nonspecific default, returned when none of the more specific NDIS_STATUS_XXX caused NDIS or the underlying network adapter driver to fail the request.

NDIS_STATUS_OPEN_ERROR

An error of type NDIS_STATUS_XXX caused the error.

NDIS_STATUS_FAILURE

The miniport could not be reconfigured.

Remarks

As an internal driver function, MiniportReconfigure might be called from MiniportInitialize to reconfigure a network adapter 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 network adapters or software-configurable network adapters.

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 until its caller, MiniportInitialize, returns control.

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

Requirements

Header

externs.h

See Also

Reference

NDIS 5.x Legacy Functions
MiniportInitialize
NdisMRegisterInterrupt
NdisMSetAttributes
NdisMSetAttributesEx
NdisOpenConfiguration
NDIS 5.x Legacy Reference