Re: [PATCH] Revert "ath: add support for special 0x0 regulatory domain"

From: "Félix Sipma" <felix+kernel@gueux.org>
To: Jouni Malinen <jkmalinen@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: [PATCH] Revert "ath: add support for special 0x0 regulatory domain"
Date: Thu, 29 Oct 2020 15:06:16 +0100	[thread overview]
Message-ID: <20201029140616.GG515433@capeo.gueux.org> (raw)
In-Reply-To: <CANe27jKpYm29QOjYOZ_jwHiRxuWx66J+th8-zgbXK4geiCU0_Q@mail.gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 1070 bytes --]

Hi,

Thanks for your detailed answer.

I made a detailed report, with dmesg outputs of different 
kernel/firmware-atheros and wireless-regdb combinations at 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970679

Massimo Maggi pointed me to this ath10k issue on the last message.

Regards,

On 2020-10-22 23:28+0300, Jouni Malinen wrote:
>What is the exact issue you are seeing?
>
>> Is there something preventing
>>
>> https://patchwork.kernel.org/project/ath10k/patch/20200527165718.129307-1-briannorris@chromium.org/
>> from being merged?
>
>That seems to have a risk of mapping the default country code (CTRY_DEFAULT
>is defined to be 0 in regd.h) being mapped to something else than a safe
>world roaming case and this could have an impact throughout all drivers
>using the generic ath/regd.c implementation. It looks like the correct
>thing to do is to map an unexpected value to the safest option instead of
>allowing this to be mapped to something that could end up enabling
>incorrect regulatory rules.
>
>- Jouni

-- 
Félix

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k