ath10k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Bryce Allen <bryce+list-ath10k@bda.space>
To: ath10k@lists.infradead.org
Subject: Re: Revert: ath: add support for special 0x0 regulatory domain
Date: Wed, 1 Sep 2021 18:37:04 -0400	[thread overview]
Message-ID: <f1102f00-95d3-3fe0-c9e4-cb53d51827d2@bda.space> (raw)

To handle my two pcengines routers with Compex cards hit by the 0x0 reg 
domain issue, I created some DKMS packages, one for Debian 11 bullseye 
(5.10) and one for the Ubuntu 20.04 HWE kernel (5.11):

https://github.com/bd4/athregd-dkms

Thanks to sparks71 for an example dkms.conf on how to do this. I just 
copied the drivers/net/wireless/ath directory out of the unpacked 
tarball from distro's linux-source package, removed everything except 
for ath9k/10k which are the cards I have and seem to be affected, and 
updated dkms.conf with desired version and modules.

I am using the module param patch from here:
https://gist.github.com/BigNerd95/0be0a5b52a16524a78fc768f0d208a74

It seems to work, but I still get tainted kernel warnings followed by an 
unpleasant stack dump in dmesg.

Cheers,
Bryce

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

             reply	other threads:[~2021-09-01 22:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01 22:37 Bryce Allen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-22 16:49 Revert: ath: add support for special 0x0 regulatory domain Andrey Skvortsov
2021-08-23 17:23 ` Brian Norris
2021-08-23 20:19   ` Andrey Skvortsov
2021-08-23 21:06     ` Brian Norris
2021-08-24  8:00       ` Alvin Šipraga
2022-03-29 21:06         ` Brian Norris
2022-03-29 21:21           ` Alvin Šipraga
2022-03-30  5:35           ` Kalle Valo
2021-08-23 18:15 ` Peter Oh
2021-08-23 20:39   ` Andrey Skvortsov

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=f1102f00-95d3-3fe0-c9e4-cb53d51827d2@bda.space \
    --to=bryce+list-ath10k@bda.space \
    --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 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).