| commit | 294196ab22c91da974ba1f40d0a7cdcb0b3e6bc3 | |
| author | Luis R. Rodriguez <lrodriguez@atheros.com> | |
| Sat, 2 May 2009 04:37:20 +0000 (2 00:37 -0400) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Wed, 20 May 2009 18:46:23 +0000 (20 14:46 -0400) | ||
| tree | 10301cf8cff8c6bfa1db351f5570b9b182ad8499 | treesnapshot (tar.gz zip) |
| parent | 768777ea1118f6ff3f1a013557e7bc4f5d2683a4 | commitdiff |
cfg80211: check allowed channel type upon userspace requests
Thanks to nl80211 userspace can be very 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.
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Thanks to nl80211 userspace can be very 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.
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
| net/wireless/nl80211.c | diffblobblamehistory |