Oops, forgot to add Michael, adding him now. Michael, just a sanity check for you. What Johannes is saying is that regulatory wise for the 2.4 GHz band on channels 1-11 and on 5 GHz on non DFS channels where we never initiate radiation we don't have a specific bandwidth restriction. Are you aware of any country restricting any 5 GHz world roaming frequency (non DFS) or channel 1-11 on 2.4 GHz in terms of bandwidth used? Luis On Thu, Dec 13, 2012 at 2:27 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxxxxx> wrote: > On Thu, Dec 6, 2012 at 8:53 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: >> From: Johannes Berg <johannes.berg@xxxxxxxxx> >> >> There aren't any channel width restrictions in the >> 2.4 GHz band (except the natural ones by the (sub)band >> boundaries), nor do default restrictions in the 5 GHz >> band make sense when limited to passive scan/no IBSS >> etc. >> >> Allow passing NL80211_NO_REG_BANDWIDTH_LIMIT as the >> max_bandwidth_khz and make that mean no restrictions. >> Use it for the default world roaming regdomain. >> >> Also make the awk script accept "NL" for "no limit" >> and substitute NL80211_NO_REG_BANDWIDTH_LIMIT. >> >> Signed-off-by: Johannes Berg <johannes.berg@xxxxxxxxx> > > For 2.4 GHz this seems fine. For 5 GHz, just to clarify for Michael, > the changes you are making are for non-DFS channels, and for the > channels where we always never initiate radiation and just world roam > unless we get a beacon hint. That is the world regulatory domain > enabled 5 GHz channels that are non-DFS. > > Michael, just a sanity check for you. What Johannes is saying is that > regulatory wise for the 2.4 GHz band on channels 1-11 and on 5 GHz on > non DFS channels where we never initiate radiation we don't have a > specific bandwidth restriction. Are you aware of any country > restricting any 5 GHz world roaming frequency (non DFS) or channel > 1-11 on 2.4 GHz in terms of bandwidth used? > > 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
