Received: by 2002:a17:90a:88:0:0:0:0 with SMTP id a8csp178228pja; Fri, 22 Nov 2019 05:06:13 -0800 (PST) X-Google-Smtp-Source: APXvYqxkzq/RhbMG7RPVD0gfg4xvxEY6K2+2ivgc6NKVWvUyq5LZEB2zgt1tUz1AtHF75zP66ZoS X-Received: by 2002:a50:b632:: with SMTP id b47mr933298ede.289.1574427973234; Fri, 22 Nov 2019 05:06:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574427973; cv=none; d=google.com; s=arc-20160816; b=BzxCufrEAnVMB66J32CEdSmerw9jQcGwJhdW0J0EmIIc0SlN/fYcmnW+gflJHMEc6p 3Lq22zweDesIS8bwIcpGhNligq1x4FxN1M6TjpgllEH0CWuZKbCBcochxwILywkoJgDY 4b72xpV4hKPW5eLvtBdxif54CsrThf9R8xbpwF4KXF5yAESLXQMsrq4Fi+RKXmpk9OYT ahFx+DwL4+B2T0IplcEFSnicOTJeyg88Cu4xUoHobs0rYNjXqumICJNJ2Mo7gMmNVjoG K1viThxZ1M2LQqYE2rfWavoWXfT8C+pubZzsvOBKVhRyZfHaeSHvH3Eefky7siG9yQNO 4qWA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=ONzcnu3Uz0Q87eUAPibsaooXscuoZp87188/nHMhJks=; b=s7pVeRza7eE9Gw0SO5SxQV+tLFt/yW2tagbC5r4wcBuiNnc0qVaaMrzG68ZVr16ovT 91Da5sR6YdVRyx5MvMfajD7TPvbmWmorh7smw+f75sHFcO9wdnfJmCe4eNd8TC+jEG2B 5IW+Pqs/wNpTvfTXQHYpU9+LXpfCIJyDrQ/g4zq+PmUITOZlvQBONBHUS5PzDevaokP1 IrzfABFCVGROBSiLCbpxv1U6w6luW737JLXrZ11fMCg2kB6iR3LBT25f50L7Foc2gu4L Nl4ShWVhhlGvqI2JM/Fyg27i7fT3cFyjUT2b5vkvq3XCYiV/fnZgbmx7+mMs1feZpgYQ Y2IQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n29si5436961edb.220.2019.11.22.05.05.46; Fri, 22 Nov 2019 05:06:13 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727008AbfKVNCt (ORCPT + 99 others); Fri, 22 Nov 2019 08:02:49 -0500 Received: from s3.sipsolutions.net ([144.76.43.62]:45170 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726548AbfKVNCt (ORCPT ); Fri, 22 Nov 2019 08:02:49 -0500 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.92.3) (envelope-from ) id 1iY8a8-0003rO-7Y; Fri, 22 Nov 2019 14:02:40 +0100 Message-ID: <7d43bbc0dfeb040d3e0468155858c4cbe50c0de2.camel@sipsolutions.net> Subject: Re: [PATCH] mac80211_hwsim: set the maximum EIRP output power for 5GHz From: Johannes Berg To: Ramon Fontes Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-wireless , kvalo@codeaurora.org, davem@davemloft.net Date: Fri, 22 Nov 2019 14:02:37 +0100 In-Reply-To: (sfid-20191122_135302_082448_33FD13BE) References: <20191108152013.13418-1-ramonreisfontes@gmail.com> (sfid-20191122_135302_082448_33FD13BE) Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Fri, 2019-11-22 at 09:52 -0300, Ramon Fontes wrote: > > How is hwsim related to ETSI? What does it matter? > > It's well known that the frequency bands 2,4 GHz and 5 GHz are mainly > used by Radio LANs and in many cases, the deployed technology is based > on the IEEE 802.11 standards family. However, other technologies such > as LTE-LAA are deployed in those frequency bands as well. That said, > considering that hwsim is an excellent module that can be used in > different network simulation scenarios; that it is not only used in > North America; and also considering that some regulatory power limits > are taken from the ETSI standards, why not set a maximum value > supported by a renowned Institute? Without this new value, regdomain > will not work as expected for some countries. Right, so the commit log should say that it should be incremented to allow regdb to work, rather than worry about ETSI specifics? Or maybe this limit should just be removed entirely? johannes