Return-path: Received: from mail-la0-f50.google.com ([209.85.215.50]:35075 "EHLO mail-la0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754226AbaBUXIs (ORCPT ); Fri, 21 Feb 2014 18:08:48 -0500 Received: by mail-la0-f50.google.com with SMTP id ec20so2858027lab.23 for ; Fri, 21 Feb 2014 15:08:47 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <1391071940-4296-1-git-send-email-janusz.dziedzic@tieto.com> <1392880090.5073.2.camel@jlt4.sipsolutions.net> From: "Luis R. Rodriguez" Date: Fri, 21 Feb 2014 15:08:27 -0800 Message-ID: (sfid-20140222_000857_485836_BB9F2D76) Subject: Re: [PATCH v4] cfg80211: regulatory introduce maximum bandwidth calculation To: Janusz Dziedzic Cc: Johannes Berg , linux-wireless Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, Feb 19, 2014 at 11:25 PM, Janusz Dziedzic wrote: > On 20 February 2014 08:08, Johannes Berg wrote: >> On Thu, 2014-02-20 at 07:07 +0100, Janusz Dziedzic wrote: >> >>> > 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-kernel + new wireless-regdb + new crda. >>> In case of AUTO we will not set NL80211_ATTR_FREQ_RANGE_MAX_BW we will >>> get -EINVAL >> >> That seems like a problem. >> > So, we can always add NL80211_ATTR_FREQ_RANGE_MAX_BW set as 0 in crda. > Then all channels where BW=0 will be HT20 only for old kernel. That also seems like a problem. Luis