archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <>
To: Kalle Valo <>
Cc: Sustek Goran <>,
	ath10k <>,
	Wen Gong <>
Subject: Re: [PATCH] ath: add support for special 0x0 regulatory domain
Date: Wed, 23 Dec 2020 10:18:45 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Dec 23, 2020 at 3:02 AM Kalle Valo <> wrote:
> Brian Norris <> writes:
> > Kalle is still planning on applying my revert patch someday, I think:
> >
> >
> >
> > We just have to wait.
> Actually I don't see how I could apply the revert due to the regulatory
> problems explained by Jouni[1]. We cannot break regulatory rules.
> [1]

Thanks for pointing that out; I hadn't noticed that thread.

I'm not sure I totally agree with Jouni's logic there, but
(a) I don't have a huge stake in that (because for systems I care
about, I make sure the hardware gets shipped out with the correct
module programming) and
(b) it's probably best if discussion mostly stays on that thread.

But I still can't help myself: that feels like retroactive logic that
doesn't make sense. Jouni seems to imply that every module ever
shipped *must* have a programmed country code in order to comply with
regulations. My understanding is that systems could have been
compliant without such a country code (for example, shipping a
non-upstream driver; or enabling CONFIG_ATH_REG_DYNAMIC_USER_REG_HINTS
and specifying logic from user space; or other creative solutions
[1]). It's probably not ideal (because mainline Linux now doesn't
really know what to do), but possible. It unfortunately leaves a
sticky situation for these users, because they have to figure out how
to retroactively patch back in the original manufacturer's regulatory


[1] I am quite familiar with a line of APs that ships this solution
(i.e., pulling its country code from the Device Tree, because the boot
flash has information about the country it was provisioned for):
I don't know what the module's EEPROM contains, but they're not relying on it.

ath10k mailing list

  reply	other threads:[~2020-12-23 18:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2020-12-22  3:42 ` [PATCH] ath: add support for special 0x0 regulatory domain Wen Gong
2020-12-22 18:30   ` Brian Norris
2020-12-23 11:01     ` Kalle Valo
2020-12-23 18:18       ` Brian Norris [this message]
2021-01-04 12:10       ` Alvin Šipraga
     [not found] <>
2019-12-02 10:08 ` Kalle Valo
     [not found] ` <>
2019-12-02 10:14   ` wgong
     [not found]   ` <>
2019-12-02 10:24     ` Kalle Valo
2019-11-29  7:34 Wen Gong

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