On Mon, Apr 8, 2013 at 11:51 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Mon, 2013-04-08 at 22:52 -0700, Luis R. Rodriguez wrote: >> From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxxxxxxxx> >> >> For VHT, the wider bandwidths (up to 160 MHz) need >> to be allowed. Since world roaming only covers the >> case of connecting to an AP, it can be opened up >> there, we will rely on the AP to know the local >> regulations. >> >> Based on a patch by Johannes Berg for upstream Linux. > >> --- a/db.txt >> +++ b/db.txt >> @@ -6,10 +6,10 @@ country 00: >> # Channel 14. Only JP enables this and for 802.11b only >> (2474 - 2494 @ 20), (3, 20), PASSIVE-SCAN, NO-IBSS, NO-OFDM >> # Channel 36 - 48 >> - (5170 - 5250 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS >> + (5170 - 5250 @ 80), (3, 20), PASSIVE-SCAN, NO-IBSS >> # NB: 5260 MHz - 5700 MHz requies DFS >> # Channel 149 - 165 >> - (5735 - 5835 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS >> + (5735 - 5835 @ 80), (3, 20), PASSIVE-SCAN, NO-IBSS > > I also have a separate upstream patch that I haven't sent here yet to > enable 160 MHz by enabling the radar channels (passively), see below; > any thoughts on that? Enabling it passively seems fine to me. Michael if we take care of DFS / passive scan, etc, are we still OK to use VHT160 if we find an AP that uses it on the DFS channels (assuming client follows channel change announcements, etc)? Luis -- 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
