linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Dan Williams <dcbw@redhat.com>, Steve deRosier <derosier@gmail.com>
Cc: solsTiCe d'Hiver <solstice.dhiver@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: second wifi card enforce CN reg dom
Date: Thu, 12 Apr 2018 21:01:24 +0200	[thread overview]
Message-ID: <5ACFAD04.10908@broadcom.com> (raw)
In-Reply-To: <1517ecac1d85eb746367d9db436beca2d8f47835.camel@redhat.com>

On 4/12/2018 5:52 PM, Dan Williams wrote:
> On Thu, 2018-04-12 at 08:18 -0700, Steve deRosier wrote:
>> On Thu, Apr 12, 2018 at 3:51 AM, Arend van Spriel
>> <arend.vanspriel@broadcom.com> wrote:
>>> On 4/12/2018 10:42 AM, solsTiCe d'Hiver wrote:
>>>>
>>>> Hi.
>>>>
>>>> This is beyond my comprehension that you could assert this is a
>>>> non issue.
>>>
>>>
>>> Well. I am just saying that it is by design. There is no way for
>>> the
>>> regulatory code to determine where you and your hardware actually
>>> reside so
>>> instead it takes a conservative approach.
>>>
>>
>> To say it another way: mixing regulatory domains on your host system
>> should result in a _smaller_ set of channels - ie only those channels
>> at the intersection of the two.
>>
>> And another wrinkle to consider - one of the 802.11 amendments (can't
>> remember which one) actually causes the radio to listen to the
>
> 802.11d I believe, from the early 2000s.

Correct.

Regards,
Arend

      parent reply	other threads:[~2018-04-12 19:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-10 19:57 second wifi card enforce CN reg dom solsTiCe d'Hiver
2018-04-12  7:00 ` solsTiCe d'Hiver
2018-04-12  7:48   ` Arend van Spriel
     [not found]     ` <CAE4vF2ftgMPhKEUHr2rPaobM9Dtuc-B9rtbF5tWavvrwUXA7Ag@mail.gmail.com>
2018-04-12 10:51       ` Arend van Spriel
2018-04-12 15:18         ` Steve deRosier
2018-04-12 15:52           ` Dan Williams
2018-04-12 17:05             ` solsTiCe d'Hiver
2018-04-12 17:11               ` Ben Greear
2018-04-12 17:25                 ` solsTiCe d'Hiver
2018-04-12 17:40                   ` Ben Greear
2018-04-12 18:30                   ` Steve deRosier
2018-04-12 19:25               ` Arend van Spriel
2018-04-12 19:01             ` Arend van Spriel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5ACFAD04.10908@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=dcbw@redhat.com \
    --cc=derosier@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=solstice.dhiver@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).