All of
 help / color / mirror / Atom feed
From: Julian Phillips <>
To: "" <>
Subject: Re: [PATCH] Revert "ath: add support for special 0x0 regulatory domain"
Date: Sun, 20 Dec 2020 01:32:16 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


Has a decision been reached as to whether or not this commit will be reverted? It appears to still exist in kernel 5.10. 

I too have a Compex WLE900VX QCA986x/988x 802.11ac card and am affected. I purchased the card from Switzerland and am running it in Canada.

I've been using the v5.4 LTS kernel as a temporary workaround, but given 5.10 will be the next LTS it would be helpful to have a definitive answer one way or another on this issue so those of us who are affected can plan accordingly.

The last update I'm aware of is Alvin's argument to revert the patch: .

Kind regards,

From: ath10k <> on behalf of Félix Sipma <>
Sent: October 30, 2020 8:51 AM
To: Jouni Malinen <>
Cc: <>
Subject: Re: [PATCH] Revert "ath: add support for special 0x0 regulatory domain" 
On 2020-10-30 09:20+0200, Jouni Malinen wrote:
>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?

Yes, sorry for not being clear about this.

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

So, if I understand well, the new behaviour (non working AP with ac) is 
expected, given that the device was not provisioned with the settings 
specifics to my zone? And to prevent people from operating an AP with 
the wrong settings, we force them to use hardware that is specific to 
their zone? If that's the intention, I'm not sure it is very effective: 
I can still buy a German wifi card and use it in France. It will 
probably suits most of the hardware vendors, though: people moving to 
another country are forced to buy new stuff and they can't buy cheaper 
stuff abroad, but, seen from another angle, it sounds like planned 

The vendor of my (new) hardware is from Switzerland, and is selling to 
(at least) everywhere in Europe, and they sell the same hardware (that 
used to work) for everybody. So, now, they are supposed to sell 
specific hardware for each country? I think the card was not 
provisioned with a specific country (I'm in France, and I tried FR, CH, 
US,  ...), so I guess I have to throw it to the bin anyway (and they 
should do the same with all their stocks).

I hope I have misunderstood your message, else I have to admit I'm a 
little disappointed... Thanks for your explanation, though!

If that's really the intention, is there a workaround for irresponsible 
people like me, who just wan't to avoid buying new stuff?


ath10k mailing list

  reply	other threads:[~2020-12-20  1:33 UTC|newest]

Thread overview: 40+ 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
2020-10-30  8:51       ` Félix Sipma
2020-12-20  1:32         ` Julian Phillips [this message]
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-07-30 12:49 ` Alvin Šipraga
2020-08-27  7:59 ` Alvin Šipraga
2020-08-27  7:59   ` Alvin Šipraga
2020-08-27 10:12   ` Kalle Valo
2020-08-27 10:12     ` Kalle Valo
2020-08-27 10:25     ` Alvin Šipraga
2020-08-27 10:25       ` Alvin Šipraga
2020-05-27 16:57 Brian Norris
2020-05-27 16:57 ` Brian Norris
2020-05-28 12:02 ` Julian Calaby
2020-05-28 12:02   ` Julian Calaby
     [not found]   ` <>
2020-06-02 18:35     ` Brian Norris
2020-06-02 18:35       ` Brian Norris
2022-03-07 17:45 ` Kalle Valo
2022-03-07 17:45   ` Kalle Valo
2022-04-23 10:52 ` Patrick Steinhardt
2022-04-23 10:52   ` Patrick Steinhardt
2022-04-25 18:54   ` Brian Norris
2022-04-25 18:54     ` Brian Norris
2022-05-09 18:16     ` Cale Collins
2022-05-09 18:16       ` Cale Collins
2022-05-11 22:52       ` Cale Collins
2022-05-11 22:52         ` Cale Collins
2022-08-30 21:56         ` Brian Norris
2022-08-30 21:56           ` Brian Norris
2022-09-19 17:24           ` Tim Harvey
2022-09-19 17:24             ` Tim Harvey
2022-09-19 23:42             ` Sergey Ryazanov
2022-09-19 23:42               ` Sergey Ryazanov
2022-09-20  5:42               ` Sebastian Gottschall
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 \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.