From: Sebastian Gottschall <s.gottschall@newmedia-net.de>
To: Sergey Ryazanov <ryazanov.s.a@gmail.com>,
Tim Harvey <tharvey@gateworks.com>
Cc: Brian Norris <briannorris@chromium.org>,
Cale Collins <ccollins@gateworks.com>,
kvalo@kernel.org, Patrick Steinhardt <ps@pks.im>,
ath10k <ath10k@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>,
Stephen McCarthy <stephen.mccarthy@pctel.com>
Subject: Re: [PATCH] Revert "ath: add support for special 0x0 regulatory domain"
Date: Tue, 20 Sep 2022 07:42:36 +0200 [thread overview]
Message-ID: <c9904373-7e20-64b6-8900-69d38f2cdef4@newmedia-net.de> (raw)
In-Reply-To: <CAHNKnsTEBr4m1SpZxnfFPWiSgxBg5HhqYCdWwm=9gp7qHXg=Pg@mail.gmail.com>
Am 20.09.2022 um 01:42 schrieb Sergey Ryazanov:
> Hello,
>
> I would like to add my 2c.
>
> On Mon, Sep 19, 2022 at 8:25 PM Tim Harvey <tharvey@gateworks.com> wrote:
>> I'm not clear if
>> there are many other cards that have this same issue.
> The list of cards with unprogrammed regdomain can be extended with
> several relatively modern models:
> * MikroTik R11e-5HacD (QCA9882 based)
> * MikroTik R11e-5HacT (QCA9880 based)
> * QNAP QWA-AC2600 (QCA9984 based) [1]
>
> As you can see these are powerful and massive cards for WISPs. Or at
> least to run as an AP. I also know a bunch of .11a/b/g/n cards with
> zero regdomain and the same target audience. Except maybe for the
> legacy Wistorn CM9, which is a relatively compact card.
>
> Also, a huge number of wireless routers and access points have
> unprogrammed regdomain. But probably this is not the case, since they
> anyway can not run a stock kernel.
>
> 1. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895333
let me add my 2c. the regdomain 0 is very common and defacto a standard
for all non oem cards on the market. i have only seen real programmed cards
as buildin cards in laptops.
beside of these zero cards there are other special regdomains available
for ath cards
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2022-09-20 5:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 16:57 [PATCH] Revert "ath: add support for special 0x0 regulatory domain" 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 [this message]
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-10-22 17:21 Félix Sipma
[not found] ` <CANe27jKpYm29QOjYOZ_jwHiRxuWx66J+th8-zgbXK4geiCU0_Q@mail.gmail.com>
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
2020-10-30 13:23 ` Alvin Sipraga
2020-12-21 13:43 ` sparks71
2020-12-21 12:15 sparks71
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=c9904373-7e20-64b6-8900-69d38f2cdef4@newmedia-net.de \
--to=s.gottschall@newmedia-net.de \
--cc=ath10k@lists.infradead.org \
--cc=briannorris@chromium.org \
--cc=ccollins@gateworks.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ps@pks.im \
--cc=ryazanov.s.a@gmail.com \
--cc=stable@vger.kernel.org \
--cc=stephen.mccarthy@pctel.com \
--cc=tharvey@gateworks.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).