ath: fix 0x6C for beaconing/passive scan flags based on country IE
authorLuis R. Rodriguez <lrodriguez@atheros.com>
Thu, 14 Apr 2011 21:55:36 +0000 (14:55 -0700)
committerJohn W. Linville <linville@tuxdriver.com>
Tue, 19 Apr 2011 19:38:02 +0000 (15:38 -0400)
The 0x6C regulatory domain is just like the 0x6A regulatory
domain but differs in that 0x6C will allow adhoc and active
scan on its channels only if we are associated to an AP
with a country IE that allows those channels. The
ath_reg_apply_beaconing_flags() does just this -- we respect
the manufacturer's intent on only enabling beaconing modes
of operation if and only if blessed by the country IE.

Cc: David Quan <david.quan@atheros.com>
Cc: Senthil Balasubramanian <senthilkumar@atheros.com>
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
drivers/net/wireless/ath/regd.c

index 7e3b29015dda8e6574ecf6e9f143092dbe5e96f7..02b896208b1adc3a40a9e457ed20d14103e06e14 100644 (file)
@@ -334,6 +334,7 @@ static void ath_reg_apply_world_flags(struct wiphy *wiphy,
        case 0x63:
        case 0x66:
        case 0x67:
+       case 0x6C:
                ath_reg_apply_beaconing_flags(wiphy, initiator);
                break;
        case 0x68: