2007-05-05 20:45:53 +02:00
|
|
|
config MAC80211
|
|
|
|
|
tristate "Generic IEEE 802.11 Networking Stack (mac80211)"
|
2009-06-03 18:30:31 +02:00
|
|
|
depends on CFG80211
|
2007-05-05 20:45:53 +02:00
|
|
|
select CRYPTO
|
|
|
|
|
select CRYPTO_ECB
|
|
|
|
|
select CRYPTO_ARC4
|
|
|
|
|
select CRYPTO_AES
|
|
|
|
|
select CRC32
|
|
|
|
|
select WIRELESS_EXT
|
|
|
|
|
---help---
|
2007-12-21 06:44:59 +01:00
|
|
|
This option enables the hardware independent IEEE 802.11
|
|
|
|
|
networking stack.
|
2007-05-05 20:45:53 +02:00
|
|
|
|
2009-06-03 18:30:31 +02:00
|
|
|
comment "CFG80211 needs to be enabled for MAC80211"
|
|
|
|
|
depends on CFG80211=n
|
|
|
|
|
|
2009-04-16 13:27:42 +02:00
|
|
|
config MAC80211_DEFAULT_PS
|
|
|
|
|
bool "enable powersave by default"
|
|
|
|
|
depends on MAC80211
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This option enables powersave mode by default.
|
|
|
|
|
|
|
|
|
|
If this causes your applications to misbehave you should fix your
|
|
|
|
|
applications instead -- they need to register their network
|
|
|
|
|
latency requirement, see Documentation/power/pm_qos_interface.txt.
|
|
|
|
|
|
|
|
|
|
config MAC80211_DEFAULT_PS_VALUE
|
|
|
|
|
int
|
|
|
|
|
default 1 if MAC80211_DEFAULT_PS
|
|
|
|
|
default 0
|
|
|
|
|
|
2008-01-02 15:17:03 +01:00
|
|
|
menu "Rate control algorithm selection"
|
|
|
|
|
depends on MAC80211 != n
|
2007-12-19 01:26:16 +01:00
|
|
|
|
2008-06-26 12:38:13 +02:00
|
|
|
config MAC80211_RC_PID
|
|
|
|
|
bool "PID controller based rate control algorithm" if EMBEDDED
|
|
|
|
|
---help---
|
|
|
|
|
This option enables a TX rate control algorithm for
|
|
|
|
|
mac80211 that uses a PID controller to select the TX
|
|
|
|
|
rate.
|
|
|
|
|
|
2008-10-05 18:07:45 +02:00
|
|
|
config MAC80211_RC_MINSTREL
|
2008-11-15 02:44:53 +01:00
|
|
|
bool "Minstrel" if EMBEDDED
|
|
|
|
|
default y
|
2008-10-05 18:07:45 +02:00
|
|
|
---help---
|
|
|
|
|
This option enables the 'minstrel' TX rate control algorithm
|
|
|
|
|
|
2007-12-19 01:26:16 +01:00
|
|
|
choice
|
|
|
|
|
prompt "Default rate control algorithm"
|
2008-11-15 02:44:53 +01:00
|
|
|
default MAC80211_RC_DEFAULT_MINSTREL
|
2007-12-19 01:26:16 +01:00
|
|
|
---help---
|
|
|
|
|
This option selects the default rate control algorithm
|
|
|
|
|
mac80211 will use. Note that this default can still be
|
2009-01-26 11:12:25 +01:00
|
|
|
overridden through the ieee80211_default_rc_algo module
|
2008-01-02 15:17:03 +01:00
|
|
|
parameter if different algorithms are available.
|
2007-12-19 01:26:16 +01:00
|
|
|
|
|
|
|
|
config MAC80211_RC_DEFAULT_PID
|
|
|
|
|
bool "PID controller based rate control algorithm"
|
2008-06-26 12:38:13 +02:00
|
|
|
depends on MAC80211_RC_PID
|
2007-12-19 01:26:16 +01:00
|
|
|
---help---
|
|
|
|
|
Select the PID controller based rate control as the
|
|
|
|
|
default rate control algorithm. You should choose
|
|
|
|
|
this unless you know what you are doing.
|
|
|
|
|
|
2008-10-05 18:07:45 +02:00
|
|
|
config MAC80211_RC_DEFAULT_MINSTREL
|
|
|
|
|
bool "Minstrel"
|
|
|
|
|
depends on MAC80211_RC_MINSTREL
|
|
|
|
|
---help---
|
|
|
|
|
Select Minstrel as the default rate control algorithm.
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 01:26:16 +01:00
|
|
|
endchoice
|
2007-10-28 14:17:44 +01:00
|
|
|
|
2007-12-19 01:26:16 +01:00
|
|
|
config MAC80211_RC_DEFAULT
|
|
|
|
|
string
|
2008-10-05 18:07:45 +02:00
|
|
|
default "minstrel" if MAC80211_RC_DEFAULT_MINSTREL
|
2008-11-15 02:44:53 +01:00
|
|
|
default "pid" if MAC80211_RC_DEFAULT_PID
|
2007-12-19 01:26:16 +01:00
|
|
|
default ""
|
|
|
|
|
|
2008-01-02 15:17:03 +01:00
|
|
|
endmenu
|
2007-12-19 01:25:57 +01:00
|
|
|
|
2008-02-23 15:17:21 +01:00
|
|
|
config MAC80211_MESH
|
|
|
|
|
bool "Enable mac80211 mesh networking (pre-802.11s) support"
|
2008-02-29 21:13:38 +01:00
|
|
|
depends on MAC80211 && EXPERIMENTAL
|
mac80211: disable mesh
My kvm instance was complaining a lot about sleeping
in atomic contexts in the mesh code, and it turns out
that both mesh_path_add() and mpp_path_add() need to
be able to sleep (they even use synchronize_rcu()!).
I put in a might_sleep() to annotate that, but I see
no way, at least right now, of actually making sure
those functions are only called from process context
since they are both called during TX and RX and the
mesh code itself even calls them with rcu_read_lock()
"held".
Therefore, let's disable it completely for now.
It's possible that I'm only seeing this because the
hwsim's beaconing is broken and thus the peers aren't
discovered right away, but it is possible that this
happens even if beaconing is working, for a peer that
doesn't exist or so.
It should be possible to solve this by deferring the
freeing of the tables to call_rcu() instead of using
synchronize_rcu(), and also using atomic allocations,
but maybe it makes more sense to rework the code to
not call these from atomic contexts and defer more of
the work to the workqueue. Right now, I can't work on
either of those solutions though.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2009-07-10 11:38:14 +02:00
|
|
|
depends on BROKEN
|
2008-02-23 15:17:21 +01:00
|
|
|
---help---
|
2008-02-25 10:13:31 +01:00
|
|
|
This options enables support of Draft 802.11s mesh networking.
|
|
|
|
|
The implementation is based on Draft 1.08 of the Mesh Networking
|
|
|
|
|
amendment. For more information visit http://o11s.org/.
|
2008-02-23 15:17:21 +01:00
|
|
|
|
|
|
|
|
|
2007-05-05 20:45:53 +02:00
|
|
|
config MAC80211_LEDS
|
|
|
|
|
bool "Enable LED triggers"
|
2008-04-28 00:34:55 +02:00
|
|
|
depends on MAC80211
|
|
|
|
|
select NEW_LEDS
|
|
|
|
|
select LEDS_TRIGGERS
|
2007-05-05 20:45:53 +02:00
|
|
|
---help---
|
2007-12-21 06:44:59 +01:00
|
|
|
This option enables a few LED triggers for different
|
|
|
|
|
packet receive/transmit events.
|
2007-05-05 20:45:53 +02:00
|
|
|
|
2007-05-05 20:46:38 +02:00
|
|
|
config MAC80211_DEBUGFS
|
|
|
|
|
bool "Export mac80211 internals in DebugFS"
|
|
|
|
|
depends on MAC80211 && DEBUG_FS
|
|
|
|
|
---help---
|
|
|
|
|
Select this to see extensive information about
|
|
|
|
|
the internal state of mac80211 in debugfs.
|
|
|
|
|
|
|
|
|
|
Say N unless you know you need this.
|
|
|
|
|
|
2008-06-30 15:10:46 +02:00
|
|
|
menuconfig MAC80211_DEBUG_MENU
|
|
|
|
|
bool "Select mac80211 debugging features"
|
|
|
|
|
depends on MAC80211
|
|
|
|
|
---help---
|
|
|
|
|
This option collects various mac80211 debug settings.
|
|
|
|
|
|
2008-01-29 16:57:51 +01:00
|
|
|
config MAC80211_DEBUG_PACKET_ALIGNMENT
|
|
|
|
|
bool "Enable packet alignment debugging"
|
2008-06-30 15:10:46 +02:00
|
|
|
depends on MAC80211_DEBUG_MENU
|
|
|
|
|
---help---
|
2008-01-29 16:57:51 +01:00
|
|
|
This option is recommended for driver authors and strongly
|
|
|
|
|
discouraged for everybody else, it will trigger a warning
|
|
|
|
|
when a driver hands mac80211 a buffer that is aligned in
|
|
|
|
|
a way that will cause problems with the IP stack on some
|
|
|
|
|
architectures.
|
|
|
|
|
|
|
|
|
|
Say N unless you're writing a mac80211 based driver.
|
|
|
|
|
|
2008-06-30 15:10:46 +02:00
|
|
|
config MAC80211_NOINLINE
|
|
|
|
|
bool "Do not inline TX/RX handlers"
|
|
|
|
|
depends on MAC80211_DEBUG_MENU
|
2007-05-05 20:45:53 +02:00
|
|
|
---help---
|
2008-06-30 15:10:46 +02:00
|
|
|
This option affects code generation in mac80211, when
|
|
|
|
|
selected some functions are marked "noinline" to allow
|
|
|
|
|
easier debugging of problems in the transmit and receive
|
|
|
|
|
paths.
|
|
|
|
|
|
|
|
|
|
This option increases code size a bit and inserts a lot
|
|
|
|
|
of function calls in the code, but is otherwise safe to
|
|
|
|
|
enable.
|
2007-05-05 20:45:53 +02:00
|
|
|
|
2008-06-30 15:10:46 +02:00
|
|
|
If unsure, say N unless you expect to be finding problems
|
|
|
|
|
in mac80211.
|
|
|
|
|
|
|
|
|
|
config MAC80211_VERBOSE_DEBUG
|
|
|
|
|
bool "Verbose debugging output"
|
|
|
|
|
depends on MAC80211_DEBUG_MENU
|
|
|
|
|
---help---
|
|
|
|
|
Selecting this option causes mac80211 to print out
|
|
|
|
|
many debugging messages. It should not be selected
|
|
|
|
|
on production systems as some of the messages are
|
|
|
|
|
remotely triggerable.
|
|
|
|
|
|
|
|
|
|
Do not select this option.
|
2007-12-17 01:09:26 +01:00
|
|
|
|
|
|
|
|
config MAC80211_HT_DEBUG
|
2008-06-30 15:10:46 +02:00
|
|
|
bool "Verbose HT debugging"
|
|
|
|
|
depends on MAC80211_DEBUG_MENU
|
2007-12-21 06:44:59 +01:00
|
|
|
---help---
|
|
|
|
|
This option enables 802.11n High Throughput features
|
|
|
|
|
debug tracing output.
|
|
|
|
|
|
2008-06-30 15:10:46 +02:00
|
|
|
It should not be selected on production systems as some
|
|
|
|
|
of the messages are remotely triggerable.
|
2007-05-05 20:45:53 +02:00
|
|
|
|
2008-06-30 15:10:46 +02:00
|
|
|
Do not select this option.
|
|
|
|
|
|
|
|
|
|
config MAC80211_TKIP_DEBUG
|
|
|
|
|
bool "Verbose TKIP debugging"
|
|
|
|
|
depends on MAC80211_DEBUG_MENU
|
|
|
|
|
---help---
|
|
|
|
|
Selecting this option causes mac80211 to print out
|
|
|
|
|
very verbose TKIP debugging messages. It should not
|
|
|
|
|
be selected on production systems as those messages
|
|
|
|
|
are remotely triggerable.
|
|
|
|
|
|
|
|
|
|
Do not select this option.
|
|
|
|
|
|
|
|
|
|
config MAC80211_IBSS_DEBUG
|
|
|
|
|
bool "Verbose IBSS debugging"
|
|
|
|
|
depends on MAC80211_DEBUG_MENU
|
|
|
|
|
---help---
|
|
|
|
|
Selecting this option causes mac80211 to print out
|
|
|
|
|
very verbose IBSS debugging messages. It should not
|
|
|
|
|
be selected on production systems as those messages
|
|
|
|
|
are remotely triggerable.
|
|
|
|
|
|
|
|
|
|
Do not select this option.
|
|
|
|
|
|
|
|
|
|
config MAC80211_VERBOSE_PS_DEBUG
|
|
|
|
|
bool "Verbose powersave mode debugging"
|
|
|
|
|
depends on MAC80211_DEBUG_MENU
|
|
|
|
|
---help---
|
|
|
|
|
Selecting this option causes mac80211 to print out very
|
|
|
|
|
verbose power save mode debugging messages (when mac80211
|
|
|
|
|
is an AP and has power saving stations.)
|
|
|
|
|
It should not be selected on production systems as those
|
|
|
|
|
messages are remotely triggerable.
|
|
|
|
|
|
|
|
|
|
Do not select this option.
|
|
|
|
|
|
|
|
|
|
config MAC80211_VERBOSE_MPL_DEBUG
|
|
|
|
|
bool "Verbose mesh peer link debugging"
|
|
|
|
|
depends on MAC80211_DEBUG_MENU
|
|
|
|
|
depends on MAC80211_MESH
|
|
|
|
|
---help---
|
|
|
|
|
Selecting this option causes mac80211 to print out very
|
|
|
|
|
verbose mesh peer link debugging messages (when mac80211
|
|
|
|
|
is taking part in a mesh network).
|
|
|
|
|
It should not be selected on production systems as those
|
|
|
|
|
messages are remotely triggerable.
|
|
|
|
|
|
|
|
|
|
Do not select this option.
|
2007-05-05 20:45:53 +02:00
|
|
|
|
|
|
|
|
config MAC80211_DEBUG_COUNTERS
|
|
|
|
|
bool "Extra statistics for TX/RX debugging"
|
2008-06-30 15:10:46 +02:00
|
|
|
depends on MAC80211_DEBUG_MENU
|
|
|
|
|
depends on MAC80211_DEBUGFS
|
2007-05-05 20:45:53 +02:00
|
|
|
---help---
|
2008-06-30 15:10:46 +02:00
|
|
|
Selecting this option causes mac80211 to keep additional
|
|
|
|
|
and very verbose statistics about TX and RX handler use
|
|
|
|
|
and show them in debugfs.
|
2008-02-23 15:17:21 +01:00
|
|
|
|
2008-06-30 15:10:46 +02:00
|
|
|
If unsure, say N.
|
