Revert: ath: add support for special 0x0 regulatory domain

[Alvin Šipraga]

On 8/23/21 11:06 PM, Brian Norris wrote:
> On Mon, Aug 23, 2021 at 1:19 PM Andrey Skvortsov
> <andrej.skvortzov at gmail.com> wrote:
>> On 21-08-23 10:23, Brian Norris wrote:
>>> Maybe it needs an Nth person to submit a revert?
>>
>> Later (Dec 23, 2020) said "Actually I don't see how I could apply the
>> revert due to the regulatory problems explained by Jouni". [1]
>> I think this could be the date when your patch was marked as Rejected.
>>
>> 1. http://lists.infradead.org/pipermail/ath10k/2020-December/012370.html>> 
> Oh wow, I almost forgot about that... Too many threads. I also forgot
> that I already replied, expressing my disagreement:
> http://lists.infradead.org/pipermail/ath10k/2020-December/012372.html>> 
> But I guess it's not really expected that mainline Linux really works
> as-is on most products, unfortunately, and the maintainers don't have
> enough time or energy to provide constructive paths forward on real
> issues like this :(

Jouni gave a good explanation for why the offending patch is correct, 
but it hinges on an interpretation of country code 0x0 which seems to be 
incorrect. I followed up on that almost a year ago here[1] but the 
thread went cold after that.

Numerous people - myself included - have cited sources clearly 
indicating that 0x0 = US, NOT unset. See the same post[1] for more info.

I still think this patch should be reverted unless somebody can provide 
a source to the contrary, re: the meaning of 0x0.

It's unfortunate that this is still affecting users, particularly when 
the original author of the patch even asked for it to be reverted.[2]

	Alvin

[1] https://lists.infradead.org/pipermail/ath10k/2021-January/012374.html
[2] 
https://lore.kernel.org/ath10k/9cc7efbb3c9b29e4553a427e6f58725f@codeaurora.org/