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
next prev parent reply other threads:[~2020-10-29 14:06 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] ` <CANe27jKpYm29QOjYOZ_jwHiRxuWx66J+th8-zgbXK4geiCU0_Q@mail.gmail.com>
2020-10-29 14:06 ` Félix Sipma [this message]
2020-10-30 7:20 ` Jouni Malinen
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] ` <CAJ-Vmomx0UFEa1w2HsGMQsZb+K8hyK=Zz9cKSo7tHv5GiMc1yw@mail.gmail.com>
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:
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=20201029140616.GG515433@capeo.gueux.org \
--to=felix+kernel@gueux.org \
--cc=ath10k@lists.infradead.org \
--cc=jkmalinen@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).