NDIS_PM_CAPABILITIES - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// ntddndis.h
typedef struct _NDIS_PM_CAPABILITIES {
NDIS_OBJECT_HEADER Header;
ULONG Flags;
ULONG SupportedWoLPacketPatterns;
ULONG NumTotalWoLPatterns;
ULONG MaxWoLPatternSize;
ULONG MaxWoLPatternOffset;
ULONG MaxWoLPacketSaveBuffer;
ULONG SupportedProtocolOffloads;
ULONG NumArpOffloadIPv4Addresses;
ULONG NumNSOffloadIPv6Addresses;
NDIS_DEVICE_POWER_STATE MinMagicPacketWakeUp;
NDIS_DEVICE_POWER_STATE MinPatternWakeUp;
NDIS_DEVICE_POWER_STATE MinLinkChangeWakeUp;
ULONG SupportedWakeUpEvents;
ULONG MediaSpecificWakeUpEvents;
} NDIS_PM_CAPABILITIES, *PNDIS_PM_CAPABILITIES;
View the official Windows Driver Kit DDI referenceNo description available.
The NDIS_PM_CAPABILITIES structure specifies power management capabilities of a network adapter.
HeaderThe type, revision, and size of the NDIS_PM_CAPABILITIES structure. This member is formatted as an NDIS_OBJECT_HEADER structure.
The miniport driver must set the Type member of Header to NDIS_OBJECT_TYPE_DEFAULT. To specify the version of the NDIS_PM_CAPABILITIES structure, the driver must set the Revision member of Header to the following value:
Added various changes for NDIS 6.30.
Set the Size member to NDIS_SIZEOF_NDIS_PM_CAPABILITIES_REVISION_2.
Original version for NDIS 6.20.
Set the Size member to NDIS_SIZEOF_NDIS_PM_CAPABILITIES_REVISION_1.
FlagsA ULONG value that contains a bitwise OR of flags. For NDIS 6.20, this member is reserved for NDIS.
Starting with NDIS 6.30, the following flags are defined:
If this flag is set, the network adapter must be able to save the received packet that caused the adapter to generate a wake-up event.
If this flag is set, the miniport driver must be able to do the following with this packet after the network adapter transitions to a full-power state:
For more information about this power management capability, see NDIS Wake Reason Status Indications.
If this flag is set, the miniport driver supports NDIS selective suspend for network adapters.
For more information about this power management capability, see NDIS Selective Suspend.
SupportedWoLPacketPatternsA ULONG value that contains a bitwise OR of flags that specify the wake-on-LAN (WOL) patterns that a network adapter supports. Miniport drivers use these flags to advertise packet based WOL patterns that a network adapter supports.
For more information about this member, see the Remarks section. For more information about WOL patterns, see NDIS_PM_WOL_PATTERN.
The network adapter can generate a wake-up event when it receives a packet that matches a configured bitmap pattern.
The network adapter can generate a wake-up event when it receives a WOL magic packet. A magic packet contains within its payload a string of six bytes with a value of 0xFF, followed immediately by 16 contiguous copies of the receiving network adapter's Ethernet address.
The network adapter can generate a wake-up event when it receives an IPv4 TCP SYN packet. Remote hosts send TCP SYN packets to initiate a TCP connection to the local computer.
The network adapter can generate a wake-up event when it receives an IPv6 TCP SYN packet.
If this flag is set, the network adapter supports as wildcard values any zero-filled, or unspecified, values for IPv4 addresses and TCP/UDP ports in a WOL pattern. In this way, the wildcard value matches any IPv4 address and any port value of the incoming packet in the location that is specified by the WOL pattern.
When a network adapter supports an IPv4 based wake on LAN packet pattern, such as an IPv4 TCP SYN pattern, it must support the generation of a wake-up event if the IPv4 addresses and port values of the incoming packet match the ones that are specified in the wake-up pattern.
However, if the NDIS_PM_WOL_IPV4_DEST_ADDR_WILDCARD_SUPPORTED flag is set, the network adapter can also generate a wake-up event if the following pattern matching conditions are true:
The miniport driver must restrict wake-up events to the specified IPv4 addresses and ports unless an overlying driver enables this capability.
Note Wildcard values that are enabled by this flag can include unspecified IPv4 source and destination addresses, as well as unspecified source and destination ports.
If this flag is set, the network adapter supports as wildcard values any zero-filled, or unspecified, values for IPv6 addresses and TCP/UDP ports in a WOL pattern. In this way, the wildcard value matches any IPv6 address and any port value of the incoming packet in the location that is specified by the WOL pattern.
When a network adapter supports an IPv6 based wake on LAN packet pattern, such as an IPv6 TCP SYN pattern, it must support the generation of a wake-up event if the IPv6 addresses and port values of the incoming packet match the ones that are specified in the wake-up pattern.
However, if the NDIS_PM_WOL_IPV6_DEST_ADDR_WILDCARD_SUPPORTED flag is set, the network adapter can also generate a wake-up event if the following pattern matching conditions are true:
The miniport driver must restrict wake-up events to the specified IPv6 addresses and ports unless an overlying driver enables this capability.
Note Wildcard values that are enabled by this flag can include unspecified IPv6 source and destination addresses, as well as unspecified source and destination ports.
The network adapter can generate a wake-up event when it receives an EAPOL request identifier message.
NumTotalWoLPatternsA ULONG value that contains the total number of WOL patterns that a network adapter supports. This is the sum of "number of supported WOL protocol patterns" and "number of supported WOL bitmap patterns."
For example, if your driver supports 8 flexible bitmap patterns, IPv4 TCP SYN (via preset filter), and magic packet, then you would report 9 in NumTotalWoLPatterns. (8 bitmaps + 1 IPv4 TCP SYN = 9)
Note The total number of WOL patterns does not include the magic packet wake-up pattern.
For more information about WOL protocol patterns, see NDIS_PM_WOL_PATTERN.
MaxWoLPatternSizeA ULONG value that contains the maximum number of bytes that can be compared with a pattern.
MaxWoLPatternOffsetA ULONG value that contains the number of bytes in a packet that can be examined, starting at the beginning of the MAC header.
MaxWoLPacketSaveBufferA ULONG value that contains the number of bytes of a WOL packet that a miniport driver can save to a buffer and indicate up the driver stack. This value must be less than or equal to the size, in bytes, of the maximum transmission unit (MTU) for the network media. The driver reports the MTU size through OID query requests of OID_GEN_MAXIMUM_FRAME_SIZE.
Note This member is ignored in NDIS 6.20 and earlier versions of NDIS. Starting with NDIS 6.30, this member must contain a nonzero value if the NDIS_PM_WAKE_PACKET_INDICATION_SUPPORTED flag is set in the Flags member.
SupportedProtocolOffloadsA ULONG value that contains a bitwise OR of flags that specify the protocol offload features that a network adapter supports. Miniport drivers use these flags to report the low power protocol offload capabilities of a network adapter.
If this bit is set, the network adapter can respond to IPv4 ARP packets while it is in a low power state
For more information about the ARP protocol, see RFC 826.
If this bit is set, the network adapter can respond to IPv6 Neighbor Solicitation (NS) packets while it is in a low power state.
For more information about IPv6 NS messages, see RFC 4861.
The network adapter can respond to IEEE 802.11i Robust Security Network (RSN) re-key requests while it is in a low power state.
NumArpOffloadIPv4AddressesA ULONG value that contains the number of IPv4 addresses that the adapter supports for ARP offload.
NumNSOffloadIPv6AddressesA ULONG value that contains the number of IPv6 NS offload requests that the adapter supports. This should be at least 2.
Note Despite its name, the NumNSOffloadIPv6Addresses contains the number of supported requests, not addresses.
MinMagicPacketWakeUpSpecifies the lowest device power state from which a network adapter can signal a wake-up event on receipt of a magic packet. A magic packet contains within its payload a string of six bytes with a value of 0xFF, followed immediately by 16 contiguous copies of the receiving network adapter's MAC address.
Note Device power states are specified by a value of Dx, where D0 is the highest device power state and D3 is the lowest device power state.
The device power state is specified as one of the following NDIS_DEVICE_POWER_STATE values:
The network adapter does not support magic packet wake-ups.
Note If the MinMagicPacketWakeUp member is set to this value, the NDIS_PM_WOL_MAGIC_PACKET_SUPPORTED flag must not be set in the SupportedWoLPacketPatterns member.
The network adapter can signal a magic packet wake-up from device power state D0. Because D0 is the fully powered state, this does not cause a wake-up, but can be used as a run-time event.
Note Starting with NDIS 6.20, signaling a magic packet wake-up from NdisDeviceStateD0 is no longer supported.
The network adapter can signal a magic packet wake-up from a device power state of D1.
The network adapter can signal a magic packet wake-up from a device state of D2.
The network adapter can signal a magic packet wake-up from a device power state of D3.
MinPatternWakeUpSpecifies the lowest device power state from which a network adapter can signal a wake-up event on receipt of a network frame that contains a pattern that is specified by the protocol driver. The power state is specified as one of the following NDIS_DEVICE_POWER_STATE values:
The network adapter does not support pattern-match wake-ups.
Note If the MinPatternWakeUp member is set to this value, only the NDIS_PM_WOL_MAGIC_PACKET_SUPPORTED flag can be set in the SupportedWoLPacketPatterns member.
The network adapter can signal a pattern-match wake-up from device power state D0. Because D0 is the fully powered state, this does not cause a wake-up but can be used as a run-time event.
Note Starting with NDIS 6.20, signaling a pattern-match wake-up from NdisDeviceStateD0 is no longer supported.
The network adapter can signal a pattern-match wake-up from a device power state of D1.
The network adapter can signal a pattern-match wake-up from a device power state of D2.
The network adapter can signal a pattern-match wake-up from a device power state of D3.
MinLinkChangeWakeUpStarting with NDIS 6.20, this member specifies the lowest device power state from which a network adapter can signal a wake-up event when the link state changes from media disconnected to media connected.
Starting with NDIS 6.30, this member specifies the lowest device power state from which a network adapter can signal wake-up events. These events are specified in the SupportedWakeUpEvents member.
The power state is specified as one of the following NDIS_DEVICE_POWER_STATE values:
The network adapter does not support link change wake-ups.
Note If the MinLinkChangeWakeUp member is set to this value, theSupportedWakeUpEvents member must be set to zero.
The network adapter can signal a link change wake-up from device power state D0. Because D0 is the fully powered state, this does not cause a wake-up but can be used as a run-time event.
Note Starting with NDIS 6.20, signaling a link change wake-up from NdisDeviceStateD0 is no longer supported.
The network adapter can signal a link change wake-up from a device power state of D1.
The network adapter can signal a link change wake-up from a device power state of D2.
The network adapter can signal a link change wake-up from a device power state of D3.
SupportedWakeUpEventsA ULONG value that contains a bitwise OR of flags. These flags specify the media-independent wake-up events that a network adapter supports. These events are not specific to media type.
Starting with NDIS 6.30, the following flags are defined:
If this flag is set, the network adapter can generate a wake-up event when it becomes connected to the networking interface.
If this flag is set, the network adapter can generate a wake-up event when it becomes disconnected to the networking interface.
MediaSpecificWakeUpEventsA ULONG value that contains a bitwise OR of flags. These flags specify the media-specific wake-up events that a network adapter supports.
Starting with NDIS 6.30, the following flags are defined:
If this flag is set, the 802.11 network adapter can generate a wake-up event if it detects a service set identifier (SSID) that was specified through a network list offload (NLO).
For more information about NLO, see Wi-Fi Network List Offload.
If this flag is set, the 802.11 network adapter can generate a wake-up event if it disassociates with the access point (AP).
If this flag is set, the 802.11 network adapter can generate a wake-up event if it encounters an error during the IEEE 802.11i RSN group transient key (GTK) handshake with the AP.
If this flag is set, the 802.11 network adapter can generate a wake-up event if it receives the first frame of the IEEE 802.11i RSN 4-way handshake with the AP. This handshake is performed when the adapter authenticates with the AP.
If this flag is set, the mobile broadband (MB) network adapter can generate a wake-up event if its registration state to the MB Service has changed.
If this flag is set, the MB network adapter can generate a wake-up event if the MB Service has to be notified about the receipt of a Short Message Service (SMS) message. The adapter generates this wake-up event either after the completion of a previously issued OID_WWAN_SMS_READ query request, or the arrival of a new class-0 (flash/alert) message from the network provider as an event notification.
If this flag is set, the MB network adapter can generate a wake-up event if it receives an Unstructured Supplementary Service Data (USSD) message.
The NDIS_PM_CAPABILITIES structure is used in the PowerManagementCapabilitiesEx member of the NDIS_MINIPORT_ADAPTER_GENERAL_ATTRIBUTES and NDIS_BIND_PARAMETERS structures and in the NDIS_STATUS_PM_CAPABILITIES_CHANGE status indication.
During miniport initialization, the miniport driver initializes an NDIS_PM_CAPABILITIES structure with the power management capabilities of the network adapter hardware. The miniport driver then sets the PowerManagementCapabilitiesEx member of the NDIS_MINIPORT_ADAPTER_GENERAL_ATTRIBUTES structure to point to the initialized NDIS_PM_CAPABILITIES structure.
An overlying driver should not try to enable capabilities that a network adapter does not support. To allow an overlying driver to determine what capabilities a network adapter provides, NDIS provides the capabilities in the PowerManagementCapabilitiesEx member of the NDIS_BIND_PARAMETERS structure.
Note NDIS 6.20 drivers must use the PowerManagementCapabilitiesEx member instead of the PowerManagementCapabilities member.
The SupportedProtocolOffloads member contains flags that specify the protocol offload features that a network adapter supports. The network adapter handles these protocols in a low power state. For example, if the network adapter hardware can handle IPv4 ARP packets for the driver stack while it is in a low power state, the miniport driver sets the NDIS_PM_PROTOCOL_OFFLOAD_ARP_SUPPORTED bit in SupportedProtocolOffloads.
NDIS_MINIPORT_ADAPTER_GENERAL_ATTRIBUTES
NDIS_STATUS_PM_CAPABILITIES_CHANGE
NdisMIndicateReceiveNetBufferLists