Return-path: Received: from mail-wm0-f53.google.com ([74.125.82.53]:36242 "EHLO mail-wm0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752962AbeDLSbi (ORCPT ); Thu, 12 Apr 2018 14:31:38 -0400 Received: by mail-wm0-f53.google.com with SMTP id x82so100395wmg.1 for ; Thu, 12 Apr 2018 11:31:37 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <5ACF0F5A.3090301@broadcom.com> <5ACF3A28.4060303@broadcom.com> <1517ecac1d85eb746367d9db436beca2d8f47835.camel@redhat.com> <9e644f38-7038-b4cf-1b68-cffd1a56a3f4@candelatech.com> From: Steve deRosier Date: Thu, 12 Apr 2018 11:30:56 -0700 Message-ID: (sfid-20180412_203141_808337_E5FB8610) Subject: Re: second wifi card enforce CN reg dom To: "solsTiCe d'Hiver" Cc: Ben Greear , Dan Williams , Arend van Spriel , linux-wireless Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Apr 12, 2018 at 10:25 AM, solsTiCe d'Hiver wrote: > It's the second time that you (Ben and Steve) are implying that I > might break the law. > No implication intended. All I said is regulatory operation is constrained by laws in various jurisdictions. And how the unit behaves is likely simply following the rules programmed into it for those purposes. And, there's nothing we can do to change that. > But why are you saying that ? I am not gonna repeat myself again. > If the radio only works as CN and won't let you change it, it's probably a CN radio and is hard-coded to do that. And, the intersection of your FR regulatory domain and the CN is what it is. Have you plugged it in alone? And if so, can you get it on FR or does it stay on CN? - Steve -- Steve deRosier Cal-Sierra Consulting LLC https://www.cal-sierra.com/