archive mirror
 help / color / mirror / Atom feed
From: Jouni Malinen <>
To: "Félix Sipma" <>
Subject: Re: [PATCH] Revert "ath: add support for special 0x0 regulatory domain"
Date: Fri, 30 Oct 2020 09:20:30 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Oct 29, 2020 at 4:06 PM Félix Sipma <> wrote:
> I made a detailed report, with dmesg outputs of different
> kernel/firmware-atheros and wireless-regdb combinations at

So the issue is in not being able to operate an AP on the 5 GHz band?
That sounds like the expected behavior for any device that has not
been calibrated and provisioned for a specific country where
regulatory rules allow operation on the 5 GHz band. I understand that
this may look like a regression since the commit removed
functionality, but it feels like a bug fix to me since that
functionality should not have been enabled by default in the first
place. The goal here is to avoid inappropriate operation on the band
without explicit configuration to enable such operation. In AP
devices, the device should have been provisioned for a specific
country to be able to enforce the correct frequency range
restrictions. The safe default for a device that does not have such
explicit configuration within the WLAN component itself is to use the
world roaming mode which prevents initialization of radiation (i.e.,
does not allow AP mode to be started but allows station mode operation
to connect to an already started AP) on the 5 GHz band.

- Jouni

ath10k mailing list

  reply	other threads:[~2020-10-30  7:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 17:21 [PATCH] Revert "ath: add support for special 0x0 regulatory domain" Félix Sipma
     [not found] ` <>
2020-10-29 14:06   ` Félix Sipma
2020-10-30  7:20     ` Jouni Malinen [this message]
2020-10-30  8:51       ` Félix Sipma
2020-12-20  1:32         ` Julian Phillips
2020-10-30 13:23       ` Alvin Sipraga
2020-12-21 13:43         ` sparks71
  -- strict thread matches above, loose matches on Subject: below --
2020-12-21 12:15 sparks71
2020-07-30 12:49 Alvin Šipraga
2020-08-27  7:59 ` Alvin Šipraga
2020-08-27 10:12   ` Kalle Valo
2020-08-27 10:25     ` Alvin Šipraga
2020-05-27 16:57 Brian Norris
2020-05-28 12:02 ` Julian Calaby
     [not found]   ` <>
2020-06-02 18:35     ` Brian Norris
2022-03-07 17:45 ` Kalle Valo
2022-04-23 10:52 ` Patrick Steinhardt
2022-04-25 18:54   ` Brian Norris
2022-05-09 18:16     ` Cale Collins
2022-05-11 22:52       ` Cale Collins
2022-08-30 21:56         ` Brian Norris
2022-09-19 17:24           ` Tim Harvey
2022-09-19 23:42             ` Sergey Ryazanov
2022-09-20  5:42               ` Sebastian Gottschall

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:

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

  git send-email \
    --in-reply-to='' \ \ \ \

* 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).