On 19 February 2014 19:51, Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxxxxx> wrote: > On Thu, Jan 30, 2014 at 12:52 AM, Janusz Dziedzic > <janusz.dziedzic@xxxxxxxxx> wrote: >> >> We don't need any changes in CRDA or internal regulatory. > > What happens if an old kernel gets a new wireless-regdb with AUTO on > all of its 5 GHz regdomain for the country it using ? I see no mention > of this anywhere in the documentation and at least from the code > review I just did it seemed like we'd use 0. I hope I'm wrong as > otherwise that'd introduce a severe regression when this is introduced > to wireless-regdb. Old wireless-regdb also allow 0 :-) (the same case like last one) Old-kernel + new wireless-regdb + new crda. In case of AUTO we will not set NL80211_ATTR_FREQ_RANGE_MAX_BW we will get -EINVAL Old-kernel + new wireless-regd + old crda (will send 0): We will set on channels: IEEE80211_CHAN_NO_HT40 | IEEE80211_CHAN_NO_HT80 | IEEE80211_CHAN_NO_HT160 So, all channels where BW=0 will be HT20 only - isn't that default? BR Janusz -- 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
