struct_ieee80211_vif - per-interface data
2. SYNOPSIS ▲
structieee80211_bss_conf bss_conf; u8 addr[ETH_ALEN]; bool p2p; u8 cab_queue; u8 hw_queue[IEEE80211_NUM_ACS];
*chanctx_conf; u32 driver_flags;
3. MEMBERS ▲
type of this virtual interface
BSS configuration for this interface, either our own or the BSS weAqre associated to
address of this interface
indicates whether this AP or STA interface is a p2p interface, i.e. a GO or p2p-sta respectively
content-after-beacon (DTIM beacon really) queue, AP mode only
hardware queue for each AC
The channel context this interface is assigned to, or NULL when it is not assigned. This pointer is RCU-protected due to the TX path needing to access it; even though the netdev carrier will always be off when it is NULL there can still be races and packets could be processed after it switches back to NULL.
flags/capabilities the driver has for this interface, these need to be set (or cleared) when the interface is added or, if supported by the driver, the interface type is changed at runtime, mac80211 will never touch this field
debugfs dentry, can be used by drivers to create own per interface debug files. Note that it will be NULL for the virtual monitor interface (if that is requested.)
data area for driver use, will always be aligned to sizeof(void *).
4. DESCRIPTION ▲
Data in this structure is continually present for driver use during the life of a virtual interface.
5. AUTHOR ▲
Johannes Berg <
6. COPYRIGHT ▲