Return-path: Received: from mail.neratec.ch ([80.75.119.105]:48001 "EHLO mail.neratec.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750709Ab1I3MxD (ORCPT ); Fri, 30 Sep 2011 08:53:03 -0400 Message-ID: <4E85BBAA.5000008@neratec.com> (sfid-20110930_145307_806358_8A34CA76) Date: Fri, 30 Sep 2011 14:52:58 +0200 From: Zefir Kurtisi MIME-Version: 1.0 To: Adrian Chadd CC: "Luis R. Rodriguez" , linux-wireless , Boris Presman , Assaf Azulay , Michael Green , David Quan , Kevin Hayes , Arun Venkataraman Subject: Re: Regulatory revamp status References: <1125417094.1836.1317285426615.JavaMail.root@idefix> <4E8468AF.8000006@neratec.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 09/30/2011 01:21 PM, Adrian Chadd wrote: > On 29 September 2011 20:46, Zefir Kurtisi wrote: > >> Really? Where would be 'there' countrycode-wise? >> >> That would definitely break today's CRDA capabilities :-\ > > I -think- one or both of ETSI/FCC have different CAC/NOL requirements > for the channels which overlap the weather radars. > At least when someone took FreeBSD to get DFS certified a while ago, > the weather radar ranges were checked against a 30 minute CAC. :) > > I think it's worth defining specific DFS parameters for each frequency > range. That's what I'll be doing for FreeBSD when I revamp its > net80211 regulatory database code. > > > Adrian I was assuming that weather radars will not be supported at all but the related channels be just disabled. It is practically impossible to assure a 99.99% detection probability (as required for ETSI 1.5.1), or? E.g. to detect ETSI radar pattern 1 (10 pulses), you basically need to treat any single detected pulse as radar event. Doable, but not very useful ;) Zefir