Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

struct_ieee80211_vif(9) [centos man page]

STRUCT 
IEEE80211_VIF(9) The basic mac80211 driver inte STRUCT IEEE80211_VIF(9) NAME
struct_ieee80211_vif - per-interface data SYNOPSIS
struct ieee80211_vif { enum nl80211_iftype type; struct ieee80211_bss_conf bss_conf; u8 addr[ETH_ALEN]; bool p2p; u8 cab_queue; u8 hw_queue[IEEE80211_NUM_ACS]; struct ieee80211_chanctx_conf __rcu * chanctx_conf; u32 driver_flags; #ifdef CONFIG_MAC80211_DEBUGFS struct dentry * debugfs_dir; #endif u8 drv_priv[0]; }; MEMBERS
type type of this virtual interface bss_conf BSS configuration for this interface, either our own or the BSS we're associated to addr[ETH_ALEN] address of this interface p2p indicates whether this AP or STA interface is a p2p interface, i.e. a GO or p2p-sta respectively cab_queue content-after-beacon (DTIM beacon really) queue, AP mode only hw_queue[IEEE80211_NUM_ACS] hardware queue for each AC chanctx_conf 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. driver_flags 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_dir 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.) drv_priv[0] data area for driver use, will always be aligned to sizeof(void *). DESCRIPTION
Data in this structure is continually present for driver use during the life of a virtual interface. AUTHOR
Johannes Berg <johannes@sipsolutions.net> Author. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 STRUCT IEEE80211_VIF(9)

Check Out this Related Man Page

STRUCT 
WIRELESS_DEV(9) Device registration STRUCT WIRELESS_DEV(9) NAME
struct_wireless_dev - wireless device state SYNOPSIS
struct wireless_dev { struct wiphy * wiphy; enum nl80211_iftype iftype; struct list_head list; struct net_device * netdev; u32 identifier; struct list_head mgmt_registrations; spinlock_t mgmt_registrations_lock; struct mutex mtx; struct work_struct cleanup_work; bool use_4addr; bool p2p_started; u8 address[ETH_ALEN]; u8 ssid[IEEE80211_MAX_SSID_LEN]; u8 ssid_len; u8 mesh_id_len; u8 mesh_id_up_len; enum wext; #endif }; MEMBERS
wiphy pointer to hardware description iftype interface type list (private) Used to collect the interfaces netdev (private) Used to reference back to the netdev, may be NULL identifier (private) Identifier used in nl80211 to identify this wireless device if it has no netdev mgmt_registrations list of registrations for management frames mgmt_registrations_lock lock for the list mtx mutex used to lock data in this struct cleanup_work work struct used for cleanup that can't be done directly use_4addr indicates 4addr mode is used on this interface, must be set by driver (if supported) on add_interface BEFORE registering the netdev and may otherwise be used by driver read-only, will be update by cfg80211 on change_interface p2p_started true if this is a P2P Device that has been started address[ETH_ALEN] The address for this device, valid only if netdev is NULL ssid[IEEE80211_MAX_SSID_LEN] (private) Used by the internal configuration code ssid_len (private) Used by the internal configuration code mesh_id_len (private) Used by the internal configuration code mesh_id_up_len (private) Used by the internal configuration code wext (private) Used by the internal wireless extensions compat code DESCRIPTION
For netdevs, this structure must be allocated by the driver that uses the ieee80211_ptr field in struct net_device (this is intentional so it can be allocated along with the netdev.) It need not be registered then as netdev registration will be intercepted by cfg80211 to see the new wireless device. For non-netdev uses, it must also be allocated by the driver in response to the cfg80211 callbacks that require it, as there's no netdev registration in that case it may not be allocated outside of callback operations that return it. AUTHOR
Johannes Berg <johannes@sipsolutions.net> Author. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 STRUCT WIRELESS_DEV(9)
Man Page