| STRUCT IEEE80211_CON(9) | The basic mac80211 driver inte | STRUCT IEEE80211_CON(9) | 
NAME¶
struct_ieee80211_conf - configuration of the device
SYNOPSIS¶
struct ieee80211_conf {
  u32 flags;
  int power_level;
  int dynamic_ps_timeout;
  int max_sleep_period;
  u16 listen_interval;
  u8 ps_dtim_period;
  u8 long_frame_max_tx_count;
  u8 short_frame_max_tx_count;
  struct cfg80211_chan_def chandef;
  bool radar_enabled;
  enum ieee80211_smps_mode smps_mode;
};  
MEMBERS¶
flags
configuration flags defined above
power_level
requested transmit power (in dBm), backward compatibility
  value only that is set to the minimum of all interfaces
dynamic_ps_timeout
The dynamic powersave timeout (in ms), see the powersave
  documentation below. This variable is valid only when the CONF_PS flag is
  set.
max_sleep_period
the maximum number of beacon intervals to sleep for
  before checking the beacon for a TIM bit (managed mode only); this value will
  be only achievable between DTIM frames, the hardware needs to check for the
  multicast traffic bit in DTIM beacons. This variable is valid only when the
  CONF_PS flag is set.
listen_interval
listen interval in units of beacon interval
ps_dtim_period
The DTIM period of the AP we´re connected to, for
  use in power saving. Power saving will not be enabled until a beacon has been
  received and the DTIM period is known.
long_frame_max_tx_count
Maximum number of transmissions for a
  “long” frame (a frame not RTS protected), called
  “dot11LongRetryLimit” in 802.11, but actually means the number
  of transmissions not the number of retries
short_frame_max_tx_count
Maximum number of transmissions for a
  “short” frame, called “dot11ShortRetryLimit” in
  802.11, but actually means the number of transmissions not the number of
  retries
chandef
the channel definition to tune to
radar_enabled
whether radar detection is enabled
smps_mode
spatial multiplexing powersave mode; note that
  IEEE80211_SMPS_STATIC is used when the device is not configured for an
  HT channel. Note that this is only valid if channel contexts are not used,
  otherwise each channel context has the number of chains listed.
DESCRIPTION¶
This struct indicates how the driver shall configure the hardware.
AUTHOR¶
Johannes Berg <johannes@sipsolutions.net>
Author.
COPYRIGHT¶
| May 2024 | Kernel Hackers Manual 2.6. |