Return-path: Received: from charlotte.tuxdriver.com ([70.61.120.58]:42315 "EHLO smtp.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752909AbaETSPO (ORCPT ); Tue, 20 May 2014 14:15:14 -0400 Date: Tue, 20 May 2014 14:08:32 -0400 From: "John W. Linville" To: Janusz Dziedzic Cc: "Luis R. Rodriguez" , "wireless-regdb@lists.infradead.org" , linux-wireless Subject: Re: [PATCH] wireless-regdb: add DFS CAC time parameter Message-ID: <20140520180832.GD13981@tuxdriver.com> (sfid-20140520_201518_644762_1B148A19) References: <1399624824-9204-1-git-send-email-janusz.dziedzic@tieto.com> <20140520142453.GB13981@tuxdriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Tue, May 20, 2014 at 08:01:31PM +0200, Janusz Dziedzic wrote: > On 20 May 2014 16:24, John W. Linville wrote: > > On Tue, May 20, 2014 at 12:33:51AM -0700, Luis R. Rodriguez wrote: > >> On Fri, May 9, 2014 at 1:40 AM, Janusz Dziedzic > >> wrote: > >> > Introduce support for setting DFS CAC time > >> > in milliseconds. > >> > > >> > Eg. > >> > (5250 - 5330 @ AUTO), (20), (60000), DFS > >> > > >> > will setup CAC 60 seconds CAC time. > >> > >> Can you elaborate whether or not this will require a bump on CRDA and > >> issuing of two new wireless-regdb files for the different versions on > >> the commit log? > > > > I would really prefer not to manage two regdb binary releases. > > Fear of that is what has kept me from merging this patch. > > > I can add support for version 19 and 20 in one crda. I am not sure > this is the best option. > BTW what about versions < 19? How do we handle this this days? What about older CRDA with newer wireless-regdb? Do we need to worry about that? John -- John W. Linville Someday the world will need a hero, and you linville@tuxdriver.com might be all we have. Be ready.