From: Sebastian Bachmann <hello@reox.at>
To: ath10k@lists.infradead.org
Subject: Re: Compex WLE200NX: regdomain sanitized regression
Date: Mon, 6 Dec 2021 08:18:07 +0100 [thread overview]
Message-ID: <dc8b39ab-cf9b-728e-19e9-258155cb37b2@reox.at> (raw)
In-Reply-To: <96b3682d-71b3-ada0-6fc7-686e51609968@leemhuis.info>
Hi,
thanks everyone for the suggestions and hints to DKMS and patches!
On 01.12.2021 10:06, Thorsten Leemhuis wrote:
> This is a regression due to 2dc016599cfa ("ath: add support for special
> 0x0 regulatory domain") that seems to affect quite a few users, but
> afaics was never properly addressed. I fully understand that this might
> be a special case where Linus' "no regressions" rule can't be simply
> applied.
I asked the retailer where I bought the Compex card if they have heard
of this issue and if the cards they are currently selling have the same
problem.
They said, that all their cards they are selling have a region ID of
0x00, which they assume to be "set your own region ID using crda".
Obviously this one anecdote cannot speak for all retailers, but it seems
like this misconception affects manufacturer, retailers and users likewise.
I think blaming the manufacturer and having users suffer isn't the best
idea, however I do not have a good solution either.
What I still haven't found out is what region ID would be "set your own
region ID using crda", i.e., what region ID would give the old behaviour
with a new kernel? Do I understood it correctly, that such cards must
not exist?
I "solved" my issue now by buying an off-the-shelf access point...
Regardless, I would still love to get my hostapd based access point back
online using a current mainline kernel.
Best,
Sebastian
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2021-12-06 7:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 8:17 Compex WLE200NX: regdomain sanitized regression Sebastian Bachmann
2021-11-27 11:28 ` Thorsten Leemhuis
2021-11-27 11:28 ` Thorsten Leemhuis
2021-11-27 12:21 ` Nuno Oliveira
2021-11-27 13:25 ` Sebastian Bachmann
2021-12-01 9:06 ` Thorsten Leemhuis
2021-12-01 9:06 ` Thorsten Leemhuis
2021-12-06 7:18 ` Sebastian Bachmann [this message]
2021-12-20 10:37 ` Kalle Valo
2021-12-20 10:37 ` Kalle Valo
2021-12-20 18:31 ` Nuno Oliveira
2021-12-20 18:31 ` Nuno Oliveira
2022-02-18 11:47 ` Thorsten Leemhuis
2022-02-18 11:47 ` Thorsten Leemhuis
2022-02-24 16:22 ` Kalle Valo
2022-02-24 16:22 ` Kalle Valo
2022-02-24 16:38 ` Thorsten Leemhuis
2022-02-24 16:38 ` Thorsten Leemhuis
2022-02-24 16:47 ` Kalle Valo
2022-02-24 16:47 ` Kalle Valo
2021-11-27 16:35 ` Bryce Allen
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=dc8b39ab-cf9b-728e-19e9-258155cb37b2@reox.at \
--to=hello@reox.at \
--cc=ath10k@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.