> > > * channels are announced by adding IEs (CSA and Extended CSA) in beacons > > > * after some (configurable) time, the channel is switched > > > * with the channel switch, CSA/ECSA IEs are removed and channel information > > > is updated. > > > * Userspace calls a new command NL80211_CMD_CHANNEL_SWITCH along with channel info > > > (freq + width), whether traffic should be blocked and timing information > > > * it currently works for me [TM] on my ath9k based machine > > > > I don't really like your approach of building all the IEs in the kernel. > > There are some things, like the country-after-switch in the CSA wrapper > > (introduced in 11ac), that would be really awkward this way. > > Hmm ... OK. I have not checked 802.11ac yet (actually I don't have access to the > drafts anyway). So what we have to expect is changing the country after the switch, > or also other new things? There are a few things in the channel switch wrapper: new country, wide bandwidth channel switch, new VHT transmit power envelope. I guess the intention is to allow for extensions in the future. > > > * could other drivers (next to ath9k) work with this API? > > > > Probably not easily. Any TI folks reading this? > > I was thinking about adding another callback function or option for that for drivers > who do the channel switch internally. Then we would only need mac80211 to adapt. > > Would that help, or what would be problematic? I don't really know. If you look at what we do in managed mode now, some drivers will do the switching and report back when done. > Yeah, that would be an alternative. I've been inspired by IEEE 802.11-2012/6.3.17 > (MLME-CHANNELSWITCH) originally. :) > I think your suggestion is good for AP where we control the beacon. For IBSS it > would be a little different: when a channel switch is triggered, userspace does > not know the beacon (and will not set it). Therefore, we could only accept the > change IEs and skip the "after-switch-beacon" IEs (these would be re-generated > internally) in IBSS mode. I guess it would be similar for mesh. Yeah, agree, IBSS/mesh modes are somewhat different here, userspace doesn't really know the channel is switching at all, does it? johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
