mirror of
https://github.com/torvalds/linux.git
synced 2024-10-31 17:21:49 +00:00
f444de05d2
Currently (all tested with hwsim) you can do stupid things like setting up an AP on a certain channel, then adding another virtual interface and making that associate on another channel -- this will make the beaconing to move channel but obviously without the necessary IEs data update. In order to improve this situation, first make the configuration APIs (cfg80211 and nl80211) aware of multi-channel operation -- we'll eventually need that in the future anyway. There's one userland API change and one API addition. The API change is that now SET_WIPHY must be called with virtual interface index rather than only wiphy index in order to take effect for that interface -- luckily all current users (hostapd) do that. For monitor interfaces, the old setting is preserved, but monitors are always slaved to other devices anyway so no guarantees. The second userland API change is the introduction of a per virtual interface SET_CHANNEL command, that hostapd should use going forward to make it easier to understand what's going on (it can automatically detect a kernel with this command). Other than mac80211, no existing cfg80211 drivers are affected by this change because they only allow a single virtual interface. mac80211, however, now needs to be aware that the channel settings are per interface now, and needs to disallow (for now) real multi-channel operation, which is another important part of this patch. One of the immediate benefits is that you can now start hostapd to operate on a hardware that already has a connection on another virtual interface, as long as you specify the same channel. Note that two things are left unhandled (this is an improvement -- not a complete fix): * different HT/no-HT modes currently you could start an HT AP and then connect to a non-HT network on the same channel which would configure the hardware for no HT; that can be fixed fairly easily * CSA An AP we're connected to on a virtual interface might indicate switching channels, and in that case we would follow it, regardless of how many other interfaces are operating; this requires more effort to fix but is pretty rare after all Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
58 lines
1.1 KiB
Makefile
58 lines
1.1 KiB
Makefile
obj-$(CONFIG_MAC80211) += mac80211.o
|
|
|
|
# mac80211 objects
|
|
mac80211-y := \
|
|
main.o status.o \
|
|
sta_info.o \
|
|
wep.o \
|
|
wpa.o \
|
|
scan.o offchannel.o \
|
|
ht.o agg-tx.o agg-rx.o \
|
|
ibss.o \
|
|
mlme.o work.o \
|
|
iface.o \
|
|
rate.o \
|
|
michael.o \
|
|
tkip.o \
|
|
aes_ccm.o \
|
|
aes_cmac.o \
|
|
cfg.o \
|
|
rx.o \
|
|
spectmgmt.o \
|
|
tx.o \
|
|
key.o \
|
|
util.o \
|
|
wme.o \
|
|
event.o \
|
|
chan.o
|
|
|
|
mac80211-$(CONFIG_MAC80211_LEDS) += led.o
|
|
mac80211-$(CONFIG_MAC80211_DEBUGFS) += \
|
|
debugfs.o \
|
|
debugfs_sta.o \
|
|
debugfs_netdev.o \
|
|
debugfs_key.o
|
|
|
|
mac80211-$(CONFIG_MAC80211_MESH) += \
|
|
mesh.o \
|
|
mesh_pathtbl.o \
|
|
mesh_plink.o \
|
|
mesh_hwmp.o
|
|
|
|
mac80211-$(CONFIG_PM) += pm.o
|
|
|
|
mac80211-$(CONFIG_MAC80211_DRIVER_API_TRACER) += driver-trace.o
|
|
CFLAGS_driver-trace.o := -I$(src)
|
|
|
|
# objects for PID algorithm
|
|
rc80211_pid-y := rc80211_pid_algo.o
|
|
rc80211_pid-$(CONFIG_MAC80211_DEBUGFS) += rc80211_pid_debugfs.o
|
|
|
|
rc80211_minstrel-y := rc80211_minstrel.o
|
|
rc80211_minstrel-$(CONFIG_MAC80211_DEBUGFS) += rc80211_minstrel_debugfs.o
|
|
|
|
mac80211-$(CONFIG_MAC80211_RC_PID) += $(rc80211_pid-y)
|
|
mac80211-$(CONFIG_MAC80211_RC_MINSTREL) += $(rc80211_minstrel-y)
|
|
|
|
ccflags-y += -D__CHECK_ENDIAN__
|