greearb / ath10k-ct

Stand-alone ath10k driver based on Candela Technologies Linux kernel.
111 stars 40 forks source link

Experimenting with ath10k-ct-htt on R7800, a few questions #137

Closed graysky2 closed 4 years ago

graysky2 commented 4 years ago

Please provide this info. See this link for more info on how to gather debug info: http://www.candelatech.com/ath10k-bugs.php

Software (OS, Firmware version, kernel, driver, etc)

Hardware (NIC chipset, platform, etc)

I followed this guide to create several files both of which contain the identical content:

/lib/firmware/ath10k/fwcfg-pci-0000:01:00.0.txt
/lib/firmware/ath10k/fwcfg-pci-0001:01:00.0.txt

# cat /lib/firmware/ath10k/fwcfg-pci-0000:01:00.0.txt
vdevs = 4
peers = 100
active_peers = 100
stations = 100
rate_ctrl_objs = 7
regdom = 840
#fwname = firmware-5-htt-mgt-b.bin
fwver = 5
nohwcrypt = 0
ct_sta_mode = 0
tx_desc = 2200
#max_nss = 3
tids = 256
skid_limit = 360
max_amsdus = 3

Upon booting, I am seeing the following in dmesg and wanted to verify that it is normal:

...
[   29.831784] ath10k_pci 0001:01:00.0: DANGER! You're overriding EEPROM-defined regulatory domain
[   29.831812] ath10k_pci 0001:01:00.0: from: 0x0 to 0x348 (svc-ready-work)
[   29.839363] ath10k_pci 0001:01:00.0: Your card was not certified to operate in the domain you chose.
[   29.846302] ath10k_pci 0001:01:00.0: This might result in a violation of your local regulatory rules.
[   29.855417] ath10k_pci 0001:01:00.0: Do not ever do this unless you really know what you are doing!
...

Complete dmesg.

greearb commented 4 years ago

You are changing the regulatory domain from the default 'world' to US location (regdom = 840). This could potentially run afoul of your local regulatory regime. You could just comment out the regdom line and that warning should go away.

graysky2 commented 4 years ago

That did the trick, thank you.