On Thu, 2009-03-19 at 01:54 -0400, Luis R. Rodriguez wrote: > Thanks to nl80211 userspace can be verify specific upon device > configuration. Before processing the request for the new HT40 > channel types (HT40- or HT40+) we need to ensure we can use them > regulatory-wise. This wasn't required with wireless extensions as > specifying the channel type wasn't not available and configuration > was done towards the end implicitly upon association or reception > of beacons from the AP. For the new nl80211 we have to check this > when configuring the interfaces explicitly. > > + if (channel_type == NL80211_CHAN_HT40MINUS && > + (chan->flags & IEEE80211_CHAN_NO_HT40MINUS)) > + goto bad_res; > + else if (channel_type == NL80211_CHAN_HT40PLUS && > + (chan->flags & IEEE80211_CHAN_NO_HT40PLUS)) > + goto bad_res; > + > + /* > + * At this point we know if that if HT40 was requested > + * we are allowed to use it and the extension channel > + * exists. > + */ > + > if (channel_type == NL80211_CHAN_HT40MINUS) > sec_freq = freq - 20; > else if (channel_type == NL80211_CHAN_HT40PLUS) These checks are _already_ there. That's what I mean with duplicate information ;) I'm working on a replacement, and it's looking nice so far. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
