fuchsia.wlan.common

Indicates that device is not a real hardware device. This extension only exists to support the SYNTH value in fuchsia.hardware.ethernet/EthernetFeature.

Indicates where MAC layer is implemented.

Indicates whether device supports transmission reports.

If true, driver implements DFS procedures (e.g. vacate channel upon detecting RADAR). Based on whether the driver implements DFS procedures, higher layers may adjust their logic (e.g. to include/exclude channels that require DFS).

If true, driver responds to probe requests; otherwise MLME must respond.

If true, driver orchestrates rate selection; otherwise MLME must do so.

SAE can be handled by the driver.

SAE can be handled by SME.

If true, driver orchestrates scans; otherwise MLME must do so.

up to 8 different tx_vector for one PPDU frame. WLAN_TX_VECTOR_IDX_INVALID indicates no more entries.

Destination mac address, or addr1 in packet header.

Number of total attempts with this specific tx vector, including successful attempts. DDK assumes the number of attempts per packet will not exceed 255. (typically <= 8)

Lower bound of contention window in exponential form cw_min = 2^(ecw_min) - 1. The unit for contention window is "slot time", which is different for each standard (e.g. 9 microseconds, 13 microseconds, etc.)

Upper bound of contention window in exponential form cw_max = 2^(ecw_max) - 1. The unit for contention window is "slot time", which is different for each standard (e.g. 9 microseconds, 13 microseconds, etc.)

Arbitration Interframe Spacing Number (control wait time between sending each frame)

TXOP limit in unit of 32 microseconds

Whether admission control is mandatory

UNKNOWN

INFRASTRUCTURE

INDEPENDENT

MESH

PERSONAL

CBW20

CBW40

CBW40BELOW

CBW80

CBW160

CBW80P80

ETHERNET_DEVICE

GENERIC_NETWORK_DEVICE

LONG_GI

SHORT_GI

SOFTMAC

FULLMAC

PS_MODE_ULTRA_LOW_POWER

PS_MODE_LOW_POWER

PS_MODE_BALANCED

PS_MODE_PERFORMANCE

ACKNOWLEDGED

REJECTED_NOT_SUPPORTED

REJECTED_INCOMPATIBLE_MODE

REJECTED_ALREADY_IN_USE

REJECTED_DUPLICATE_REQUEST

ACTIVE

PASSIVE

TWO_GHZ

FIVE_GHZ

PAIRWISE

GROUP

IGTK

PEER

CLIENT

AP

MESH

DSSS

IEEE 802.11-2016 Clause 15: Direct Sequence Spread Spectrum Supports 1, 2 Mbps.

HR

IEEE 802.11-2016 Clause 16: High Rate DSSS Supports 5.5, 11 Mbps. Also referred to as ERP-CCK

OFDM

IEEE 802.11a/g or IEEE 802.11-2016 Clause 17: Orthogonal Frequency Division Multiplexing Supports 6, 9, 12, 18, 24, 36, 48, and 54 Mbps.

ERP

IEEE 802.11g or IEEE 802.11-2016 Clause 18: Extended Rate PHY Supports 1, 2, 5.5, 11, 12, 24 Mbps + optionally 6, 54 Mbps. Encompasses DSSS/HR/OFDM rates and modulation.

HT

IEEE 802.11n or IEEE 802.11-2016 Clause 19: High Throughput PHY Supports rates up to 495 Mbps.

DMG

802.11ad or IEEE 802.11-2016 Clause 20: Directional Multi-Gigabit PHY

VHT

IEEE 802.11ac or IEEE 802.11-2016 Clause 21: Very High Throughput PHY Supports rates up to 6.9 Gbps.

TVHT

IEEE 802.11af or IEEE 802.11-2016 Clause 22: Television Very High Throughput PHY Supports rates of up to 568.9 Mbps in TV spectrum

S1G

IEEE 802.11ah or IEEE 802.11-2020 Clause 23: Sub 1-GHz PHY

CDMG

IEEE 802.11aj or IEEE 802.11-2020 Clause 24: China Directional Multi-Gigabit PHY

CMMG

IEEE 802.11aj or IEEE 802.11-2020 Clause 25: China Millimeter-wave Multi-Gigabit PHY

HE

IEEE 802.11ax: High Efficiency PHY Supports rates of up to 9.6 Gbps (whew!)

SHORT_PREAMBLE

Short packet preamble.

SPECTRUM_MGMT

Spectrum management.

QOS

SHORT_SLOT_TIME

Short slot times after packet collision.

RADIO_MSMT

Radio measurement.

SIMULTANEOUS_CLIENT_AP

FAILED

ACK was not received or transmission otherwise failed.

SUCCESS

ACK was received from peer.

1

2

3

4

This constant defined the fixed length for arrays containing the capabilities for each band supported by a device driver.

This constant defines fixed length for arrays containing MAC roles supported by PHY entities.

This constant defines fixed length for arrays containing PHY types supported by PHY entities.

Information defined only within a context of association Beware the subtle interpretation of each field: they are designed to reflect the parameters safe to use within an association Many parameters do not distinguish Rx capability from Tx capability. In those cases, a capability is commonly applied to both Rx and Tx. Some parameters are distinctively for Rx only, and some are Tx only.