Important The Native 802.11 Wireless LAN interface is deprecated in Windows 10 and later. Please use the WLAN Device Driver Interface (WDI) instead. For more information about WDI, see WLAN Universal Windows driver model.
When queried, the OID_DOT11_WFD_ENUM_DEVICE_LIST object identifier (OID) requests that the miniport driver return the list of other devices within range of the Wi-Fi Direct (WFD) device. The device list is created from the cache of devices the WFD device detected during the most recent device discovery operation. Device discovery is initiated with an OID_DOT11_WFD_DISCOVER_REQUEST OID.
The data type for OID_DOT11_WFD_ENUM_DEVICE_LIST is the DOT11_BYTE_ARRAY structure.
The device list is returned in the InformationBuffer member of the MiniportOidRequest function's OidRequest parameter. Each entry in the list is in the form of a DOT11_WFD_DEVICE_ENTRY structure. The entries are placed in the ucBuffer of the DOT11_BYTE_ARRAY structure.
When this OID is queried, the miniport driver must do the following:
- Verify that the InformationBuffer member of its MiniportOidRequest function's OidRequest parameter is large enough to return the device list. For more information about this procedure, see DOT11_BYTE_ARRAY.
- The DOT11_WFD_DEVICE_ENTRY structure has a variable length. However, the miniport driver must not add padding for alignment between DOT11_WFD_DEVICE_ENTRY structures returned in the InformationBuffer member of the OidRequest parameter.
- Use the following macro for calculating the values of the uNumOfBytes and uTotalNumOfBytes members of the DOT11_BYTE_ARRAY structure:
The miniport driver may include any legacy networks discovered during a device discovery. If legacy networks are included, the information collected about the access point (AP) (infrastructure BSS networks) or peer station (independent BSS networks) should be included in the DOT11_WFD_DEVICE_ENTRY fields.
Supported starting with Windows 8.
|Windot11.h (include Windot11.h)|