Received: by 2002:a05:6358:45e:b0:b5:b6eb:e1f9 with SMTP id 30csp658551rwe; Thu, 1 Sep 2022 05:57:45 -0700 (PDT) X-Google-Smtp-Source: AA6agR7JE359Nix1+rpX2UT6C1onWrByERFV8w3NSpZlS/3ZQhNL1KoVsnlPD7sMKrsE2oQ9Zy7r X-Received: by 2002:a17:90b:38c4:b0:1fe:e5c:d7bf with SMTP id nn4-20020a17090b38c400b001fe0e5cd7bfmr8520520pjb.161.1662037065214; Thu, 01 Sep 2022 05:57:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1662037065; cv=none; d=google.com; s=arc-20160816; b=RJ45XbWR3/bCixrrPYqdf0UlCsqsa23LDmp9z8ii/DAPX60aM+nWJ74jSmpNmNWArm G/enxPP6B3pHlJ44RnnlhaoNEdNyGVXcxOXAjOWhsTs0PwgGaNqJTkQrOwY/MjZ2FRi1 qKStmEWynl431f42FUR7m4R1Soe2pFVZUTHCvVxAO5ffwxprj68dVfKjbcDydlD622Iq ogpK5AVPTQ3pPkc23nlGkgnRYUqeCSGWeUIgRkupNF4ceTuWAKB1DtE5xUdfr8iPzMQq tQvYS70LVsiX/iK9tgDndRijbM5OYD9iaUVtYTHt2SPbjpq/Lac2zu7BcGBRyNG9CDTY LHAw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=1h+DgBl3cs5xl3611sDHVyWFpJ+nCJR2bS/0uvkM9Bw=; b=EO7VqBczS4eYo13HWVTWqZjVQl7UbExstnlRVcSLRpcq3Hv5Ly04MpnkTp2Nbig1P7 MyE0UQUfyL/wGm7CRgjYnofnj5QKR5XpQkkcq2x/s6OqImnyTg2vE5LicJK2WIJKr5V9 3OCjjIBY/lQjwtMU0ScXfzls+ODeiwGqvCnopTeS8Sk5yYQbENzyiCFYg8HnpBMzjFFk YZzeX9TG7oVQDXcPt82Un5jVKP4TBgv+k+47+9gJ1g6UzQDntW171Auph/pEOIWnzc2h ej+YqvtCsVdpq2Wphi9LLu+VjDrN7wIXPpjqWZbGHK5z6T+aLEa0UAaOhHPCfTXi4g6y PQOw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=VGdRNbgN; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id rm4-20020a17090b3ec400b001fb5330d673si4973610pjb.139.2022.09.01.05.57.30; Thu, 01 Sep 2022 05:57:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=VGdRNbgN; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233052AbiIAMuq (ORCPT + 64 others); Thu, 1 Sep 2022 08:50:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38508 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233329AbiIAMun (ORCPT ); Thu, 1 Sep 2022 08:50:43 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B06C8DFE1 for ; Thu, 1 Sep 2022 05:50:38 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 70076B82566 for ; Thu, 1 Sep 2022 12:50:37 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 17DB1C43470; Thu, 1 Sep 2022 12:50:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1662036636; bh=OWtdBP4/+VXtdZ5lVRHsOHA3h+/yoWhw6ulhO3A835g=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=VGdRNbgNIFpml+QvbmtsJzIb0+vFZKtb8nrkvP3udIwWJ5e5SDQTKl37kH4mCQS2j BsNoFggY93HzVdMPCwS3SVKP9GomDz4ugCTDnGc748XaxddLV02HjLfZ6I4VTTjasS JC7VuUJYRdFIN0MFOz89XqWNKzO/5VOfwxuiv401Sj6ZThmp/376w1Cxp/QeJBACJ5 4Hjlu6DVfOtSkyeMQ35SLPfxeckOXWeo+m1C8pW7nQcd9eRCfTykvowuUo7kcSu8nl emGnBRaLuMit8fGFapsiuR5ZBeW6jm2qmicOm3LOnyIY7035pT57W8Jv+B9fiJ1Aql VA6LO/tR4vuFQ== Date: Thu, 1 Sep 2022 07:50:35 -0500 From: Seth Forshee To: Cesar Eduardo Barros Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org Subject: Re: [wireless-regdb] wireless-regdb: Update regulatory rules for Brazil (BR) Message-ID: References: <271ca023-d574-7d84-a020-ec5950fb500e@cesarb.eti.br> <2cf2cb6e-8083-9c09-c2a6-ae49424ea37a@cesarb.eti.br> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <2cf2cb6e-8083-9c09-c2a6-ae49424ea37a@cesarb.eti.br> X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Wed, Aug 31, 2022 at 11:44:17PM -0300, Cesar Eduardo Barros wrote: > Em 30/08/2022 11:18, Seth Forshee escreveu: > > On Wed, Aug 17, 2022 at 08:31:56PM -0300, Cesar Eduardo Barros wrote: > > > #(902 - 907.5 @ ???), (30) > > > #(915 - 928 @ ???), (30) > > > > For these ranges I think you should use the same bandwidth as other > > rules in the database, i.e. 2 and 16 MHz. > > I found only two entries in the database with rules for the 900MHz > frequencies: US and "world". I don't think the US rule is a good model here; > it can use 16 MHz because it's a contiguous range, but the range for Brazil > has a hole in the middle. > > Since there's nothing that a found in these rules which mention a maximum > channel width, the correct width is probably the maximum which fits on each > piece of the range. That is, > > (902 - 907.5 @ 4), (30) > (915 - 928 @ 8), (30) > > As far as I could find, the hole between 907.5 and 915 exists because there > are three 2.5 MHz-wide GSM uplink channels there. However, I also found out > that there is a proposal within ANATEL (Consulta Pública 52 from 2021) to > expand it with another uplink channel at 905 - 907.5 (there are actually > five uplink channels in that proposal, the other one is at 898.5 - 901). I > have no idea when this will become official, or whether it has already > happened (and just wasn't reflected yet in the restricted radiation rules I > had researched), and what effect it would have on 802.11ah users. > > Given the uncertainty from that change, and given that so far there are > rules for the 900 MHz range in wireless-regdb only for the USA, it might be > wise to hold it for now and apply only the rest of the changes, without > these 900 MHz ranges. Sounds good to me. > > Otherwise I think these changes look good. If you can send a patch with > > the changes I would appreciate it, otherwise let me know and I can send > > a patch. > > I will prepare a patch tomorrow. Thanks! > > -- > Cesar Eduardo Barros > cesarb@cesarb.eti.br > > > _______________________________________________ > wireless-regdb mailing list > wireless-regdb@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/wireless-regdb