Re: failed to fetch board data QCA6174

ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed

* Re: failed to fetch board data QCA6174
@ 2017-09-11 22:03 Luka Karinja
  2017-09-11 22:25 ` Ryan Hsu
  0 siblings, 1 reply; 16+ messages in thread
From: Luka Karinja @ 2017-09-11 22:03 UTC (permalink / raw)
  To: ath10k

 >
 > > Hello. I'm trying to get a M.2 QCA6174 working on my MSI B150Mortar 
motherboard. i did try all the various firmware versions from 
https://github.com/kvalo/ath10k-firmware more or less with the same 
errors as bellow
 > >
 > > in dmesg i get: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000 
from ath10k/QCA6174/hw3.0/board-2.bin
 > >
 > > when trying to get the device up i get: RTNETLINK answers: Resource 
temporarily unavailable
 > >
 > > [ 2026.219245] ath10k_pci 0000:05:00.0: pci irq msi oper_irq_mode 2 
irq_mode 0 reset_mode 0
 > > [ 2026.477510] ath10k_pci 0000:05:00.0: qca6174 hw3.2 target 
0x05030000 chip_id 0x00340aff sub 0000:0000
 > > [ 2026.477517] ath10k_pci 0000:05:00.0: kconfig debug 0 debugfs 1 
tracing 0 dfs 0 testmode 0
 > > [ 2026.478640] ath10k_pci 0000:05:00.0: firmware ver 
WLAN.RM.4.4.1-00026-QCARMSWP-1 api 6 features wowlan,ignore-otp,raw-mode 
crc32 7b90c3fc
 > > [ 2026.542196] ath10k_pci 0000:05:00.0: failed to fetch board data 
for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000 
from ath10k/QCA6174/hw3.0/board-2.bin
 > >
 >
 > Not sure what kernel and driver do you have?
 >
 > This should already fix this case - 
https://patchwork.kernel.org/patch/9486941/
 >

I have kernel 4.12.10 (Arch linux) i did try with ath10k WLAN.RM.2.4, 
4.4, 4.4.1 firmware



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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: failed to fetch board data QCA6174
  2017-09-11 22:03 failed to fetch board data QCA6174 Luka Karinja
@ 2017-09-11 22:25 ` Ryan Hsu
  2017-09-12  7:24   ` Luka Karinja
  0 siblings, 1 reply; 16+ messages in thread
From: Ryan Hsu @ 2017-09-11 22:25 UTC (permalink / raw)
  To: Luka Karinja, ath10k@lists.infradead.org

On 09/11/2017 03:03 PM, Luka Karinja wrote:

> >
> > > Hello. I'm trying to get a M.2 QCA6174 working on my MSI B150Mortar motherboard. i did try all the various firmware versions from https://github.com/kvalo/ath10k-firmware more or less with the same errors as bellow
> > >
> > > in dmesg i get: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000 from ath10k/QCA6174/hw3.0/board-2.bin
> > >
> > > when trying to get the device up i get: RTNETLINK answers: Resource temporarily unavailable
> > >
> > > [ 2026.219245] ath10k_pci 0000:05:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
> > > [ 2026.477510] ath10k_pci 0000:05:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 0000:0000
> > > [ 2026.477517] ath10k_pci 0000:05:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
> > > [ 2026.478640] ath10k_pci 0000:05:00.0: firmware ver WLAN.RM.4.4.1-00026-QCARMSWP-1 api 6 features wowlan,ignore-otp,raw-mode crc32 7b90c3fc
> > > [ 2026.542196] ath10k_pci 0000:05:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000 from ath10k/QCA6174/hw3.0/board-2.bin
> > >
> >
> > Not sure what kernel and driver do you have?
> >
> > This should already fix this case - https://patchwork.kernel.org/patch/9486941/
> >
>
> I have kernel 4.12.10 (Arch linux) i did try with ath10k WLAN.RM.2.4, 4.4, 4.4.1 firmware
>

ok, then it should be happening, would you mind enable the ATH10K_DBG_BOOT and share logs?
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/debug

-- 
Ryan Hsu

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: failed to fetch board data QCA6174
  2017-09-11 22:25 ` Ryan Hsu
@ 2017-09-12  7:24   ` Luka Karinja
  2017-09-12  7:39     ` Luka Karinja
  2017-09-12 23:14     ` Ryan Hsu
  0 siblings, 2 replies; 16+ messages in thread
From: Luka Karinja @ 2017-09-12  7:24 UTC (permalink / raw)
  To: Ryan Hsu, ath10k@lists.infradead.org



On 09/12/2017 12:25 AM, Ryan Hsu wrote:
> On 09/11/2017 03:03 PM, Luka Karinja wrote:
>
>>>> Hello. I'm trying to get a M.2 QCA6174 working on my MSI B150Mortar motherboard. i did try all the various firmware versions from https://github.com/kvalo/ath10k-firmware more or less with the same errors as bellow
>>>>
>>>> in dmesg i get: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000 from ath10k/QCA6174/hw3.0/board-2.bin
>>>>
>>>> when trying to get the device up i get: RTNETLINK answers: Resource temporarily unavailable
>>>>
>>>> [ 2026.219245] ath10k_pci 0000:05:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
>>>> [ 2026.477510] ath10k_pci 0000:05:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 0000:0000
>>>> [ 2026.477517] ath10k_pci 0000:05:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
>>>> [ 2026.478640] ath10k_pci 0000:05:00.0: firmware ver WLAN.RM.4.4.1-00026-QCARMSWP-1 api 6 features wowlan,ignore-otp,raw-mode crc32 7b90c3fc
>>>> [ 2026.542196] ath10k_pci 0000:05:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000 from ath10k/QCA6174/hw3.0/board-2.bin
>>>>
>>> Not sure what kernel and driver do you have?
>>>
>>> This should already fix this case - https://patchwork.kernel.org/patch/9486941/
>>>
>> I have kernel 4.12.10 (Arch linux) i did try with ath10k WLAN.RM.2.4, 4.4, 4.4.1 firmware
>>
> ok, then it should be happening, would you mind enable the ATH10K_DBG_BOOT and share logs?
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/debug
>
here is the log with ATH10K_DBG_BOOT

[    3.388761] ath10k_pci 0000:05:00.0: pci probe 168c:003e 0000:0000
[    3.388784] ath10k_pci 0000:05:00.0: enabling device (0000 -> 0002)
[    3.388886] ath10k_pci 0000:05:00.0: boot pci_mem 0xffffb2cc04200000
[    3.389044] ath10k_pci 0000:05:00.0: pci irq msi oper_irq_mode 2 
irq_mode 0 reset_mode 0
[    3.389061] ath10k_pci 0000:05:00.0: boot qca6174 chip reset
[    3.389062] ath10k_pci 0000:05:00.0: boot cold reset
[    3.440716] ath10k_pci 0000:05:00.0: boot cold reset complete
[    3.440718] ath10k_pci 0000:05:00.0: boot waiting target to initialise
[    3.440722] ath10k_pci 0000:05:00.0: boot target indicator 2
[    3.440728] ath10k_pci 0000:05:00.0: boot target initialised
[    3.440728] ath10k_pci 0000:05:00.0: boot warm reset
[    3.473362] ath10k_pci 0000:05:00.0: boot init ce src ring id 0 
entries 16 base_addr ffff9fcdf703e000
[    3.473375] ath10k_pci 0000:05:00.0: boot ce dest ring id 1 entries 
512 base_addr ffff9fcdf705e000
[    3.473387] ath10k_pci 0000:05:00.0: boot ce dest ring id 2 entries 
128 base_addr ffff9fcdf703f000
[    3.473400] ath10k_pci 0000:05:00.0: boot init ce src ring id 3 
entries 32 base_addr ffff9fcdf7040000
[    3.473416] ath10k_pci 0000:05:00.0: boot init ce src ring id 4 
entries 8192 base_addr ffff9fcdf7060000
[    3.473430] ath10k_pci 0000:05:00.0: boot init ce src ring id 7 
entries 2 base_addr ffff9fcdf7041000
[    3.473441] ath10k_pci 0000:05:00.0: boot ce dest ring id 7 entries 2 
base_addr ffff9fcdf7042000
[    3.473442] ath10k_pci 0000:05:00.0: boot waiting target to initialise
[    3.473445] ath10k_pci 0000:05:00.0: boot target indicator 0
[    3.483457] ath10k_pci 0000:05:00.0: boot target indicator 2
[    3.483463] ath10k_pci 0000:05:00.0: boot target initialised
[    3.503359] ath10k_pci 0000:05:00.0: boot init ce src ring id 0 
entries 16 base_addr ffff9fcdf703e000
[    3.503374] ath10k_pci 0000:05:00.0: boot ce dest ring id 1 entries 
512 base_addr ffff9fcdf705e000
[    3.503388] ath10k_pci 0000:05:00.0: boot ce dest ring id 2 entries 
128 base_addr ffff9fcdf703f000
[    3.503403] ath10k_pci 0000:05:00.0: boot init ce src ring id 3 
entries 32 base_addr ffff9fcdf7040000
[    3.503419] ath10k_pci 0000:05:00.0: boot init ce src ring id 4 
entries 8192 base_addr ffff9fcdf7060000
[    3.503435] ath10k_pci 0000:05:00.0: boot init ce src ring id 7 
entries 2 base_addr ffff9fcdf7041000
[    3.503448] ath10k_pci 0000:05:00.0: boot ce dest ring id 7 entries 2 
base_addr ffff9fcdf7042000
[    3.503449] ath10k_pci 0000:05:00.0: boot waiting target to initialise
[    3.503451] ath10k_pci 0000:05:00.0: boot target indicator 0
[    3.513458] ath10k_pci 0000:05:00.0: boot target indicator 2
[    3.513464] ath10k_pci 0000:05:00.0: boot target initialised
[    3.513464] ath10k_pci 0000:05:00.0: boot warm reset complete
[    3.513465] ath10k_pci 0000:05:00.0: boot qca6174 chip reset complete 
(cold)
[    3.513475] ath10k_pci 0000:05:00.0: boot hif power up
[    3.513480] ath10k_pci 0000:05:00.0: boot qca6174 chip reset
[    3.513481] ath10k_pci 0000:05:00.0: boot cold reset
[    3.566677] ath10k_pci 0000:05:00.0: boot cold reset complete
[    3.566678] ath10k_pci 0000:05:00.0: boot waiting target to initialise
[    3.566682] ath10k_pci 0000:05:00.0: boot target indicator 2
[    3.566687] ath10k_pci 0000:05:00.0: boot target initialised
[    3.566688] ath10k_pci 0000:05:00.0: boot warm reset
[    3.603354] ath10k_pci 0000:05:00.0: boot init ce src ring id 0 
entries 16 base_addr ffff9fcdf703e000
[    3.603366] ath10k_pci 0000:05:00.0: boot ce dest ring id 1 entries 
512 base_addr ffff9fcdf705e000
[    3.603377] ath10k_pci 0000:05:00.0: boot ce dest ring id 2 entries 
128 base_addr ffff9fcdf703f000
[    3.603390] ath10k_pci 0000:05:00.0: boot init ce src ring id 3 
entries 32 base_addr ffff9fcdf7040000
[    3.603405] ath10k_pci 0000:05:00.0: boot init ce src ring id 4 
entries 8192 base_addr ffff9fcdf7060000
[    3.603418] ath10k_pci 0000:05:00.0: boot init ce src ring id 7 
entries 2 base_addr ffff9fcdf7041000
[    3.603430] ath10k_pci 0000:05:00.0: boot ce dest ring id 7 entries 2 
base_addr ffff9fcdf7042000
[    3.603430] ath10k_pci 0000:05:00.0: boot waiting target to initialise
[    3.603433] ath10k_pci 0000:05:00.0: boot target indicator 0
[    3.613440] ath10k_pci 0000:05:00.0: boot target indicator 2
[    3.613445] ath10k_pci 0000:05:00.0: boot target initialised
[    3.633356] ath10k_pci 0000:05:00.0: boot init ce src ring id 0 
entries 16 base_addr ffff9fcdf703e000
[    3.633370] ath10k_pci 0000:05:00.0: boot ce dest ring id 1 entries 
512 base_addr ffff9fcdf705e000
[    3.633384] ath10k_pci 0000:05:00.0: boot ce dest ring id 2 entries 
128 base_addr ffff9fcdf703f000
[    3.633398] ath10k_pci 0000:05:00.0: boot init ce src ring id 3 
entries 32 base_addr ffff9fcdf7040000
[    3.633416] ath10k_pci 0000:05:00.0: boot init ce src ring id 4 
entries 8192 base_addr ffff9fcdf7060000
[    3.633433] ath10k_pci 0000:05:00.0: boot init ce src ring id 7 
entries 2 base_addr ffff9fcdf7041000
[    3.633445] ath10k_pci 0000:05:00.0: boot ce dest ring id 7 entries 2 
base_addr ffff9fcdf7042000
[    3.633446] ath10k_pci 0000:05:00.0: boot waiting target to initialise
[    3.633449] ath10k_pci 0000:05:00.0: boot target indicator 0
[    3.643827] ath10k_pci 0000:05:00.0: boot target indicator 2
[    3.643834] ath10k_pci 0000:05:00.0: boot target initialised
[    3.643834] ath10k_pci 0000:05:00.0: boot warm reset complete
[    3.643835] ath10k_pci 0000:05:00.0: boot qca6174 chip reset complete 
(cold)
[    3.643851] ath10k_pci 0000:05:00.0: boot init ce src ring id 0 
entries 16 base_addr ffff9fcdf703e000
[    3.643864] ath10k_pci 0000:05:00.0: boot ce dest ring id 1 entries 
512 base_addr ffff9fcdf705e000
[    3.643877] ath10k_pci 0000:05:00.0: boot ce dest ring id 2 entries 
128 base_addr ffff9fcdf703f000
[    3.643892] ath10k_pci 0000:05:00.0: boot init ce src ring id 3 
entries 32 base_addr ffff9fcdf7040000
[    3.643911] ath10k_pci 0000:05:00.0: boot init ce src ring id 4 
entries 8192 base_addr ffff9fcdf7060000
[    3.643925] ath10k_pci 0000:05:00.0: boot init ce src ring id 7 
entries 2 base_addr ffff9fcdf7041000
[    3.643939] ath10k_pci 0000:05:00.0: boot ce dest ring id 7 entries 2 
base_addr ffff9fcdf7042000
[    3.656678] ath10k_pci 0000:05:00.0: Hardware name qca6174 hw3.2 
version 0x5030000
[    3.656935] ath10k_pci 0000:05:00.0: boot fw request 
'ath10k/pre-cal-pci-0000:05:00.0.bin': -2
[    3.656944] ath10k_pci 0000:05:00.0: boot fw request 
'ath10k/cal-pci-0000:05:00.0.bin': -2
[    3.656945] ath10k_pci 0000:05:00.0: trying fw api 6
[    3.662928] ath10k_pci 0000:05:00.0: boot fw request 
'ath10k/QCA6174/hw3.0/firmware-6.bin': 0
[    3.662930] ath10k_pci 0000:05:00.0: found fw version 
WLAN.RM.4.4.1-00026-QCARMSWP-1
[    3.662931] ath10k_pci 0000:05:00.0: found fw timestamp 1502353467
[    3.662932] ath10k_pci 0000:05:00.0: found otp image ie (24193 B)
[    3.662932] ath10k_pci 0000:05:00.0: found fw image ie (703151 B)
[    3.662933] ath10k_pci 0000:05:00.0: found firmware features ie (2 B)
[    3.662934] ath10k_pci 0000:05:00.0: Enabling feature bit: 6
[    3.662934] ath10k_pci 0000:05:00.0: Enabling feature bit: 7
[    3.662935] ath10k_pci 0000:05:00.0: Enabling feature bit: 10
[    3.662936] ath10k_pci 0000:05:00.0: features
[    3.662937] ath10k_pci 0000:05:00.0: 00000000: c0 04 00 00 00 00 00 
00                          ........
[    3.662937] ath10k_pci 0000:05:00.0: found fw ie wmi op version 4
[    3.662938] ath10k_pci 0000:05:00.0: found fw ie htt op version 3
[    3.662939] ath10k_pci 0000:05:00.0: using fw api 6
[    3.662941] ath10k_pci 0000:05:00.0: qca6174 hw3.2 target 0x05030000 
chip_id 0x00340aff sub 0000:0000
[    3.662941] ath10k_pci 0000:05:00.0: kconfig debug 1 debugfs 1 
tracing 1 dfs 0 testmode 0
[    3.663314] ath10k_pci 0000:05:00.0: firmware ver 
WLAN.RM.4.4.1-00026-QCARMSWP-1 api 6 features wowlan,ignore-otp,raw-mode 
crc32 7b90c3fc
[    3.663315] ath10k_pci 0000:05:00.0: boot did not find a pre 
calibration file, try DT next: -2
[    3.663316] ath10k_pci 0000:05:00.0: unable to load pre cal data from 
DT: -2
[    3.663317] ath10k_pci 0000:05:00.0: could not load pre cal data: -2
[    3.663318] ath10k_pci 0000:05:00.0: boot upload otp to 0x1234 len 
24193 for board id
[    3.726143] ath10k_pci 0000:05:00.0: boot get otp board id result 
0x00000000 board_id 0 chip_id 0
[    3.726144] ath10k_pci 0000:05:00.0: board id does not exist in otp, 
ignore it
[    3.726165] ath10k_pci 0000:05:00.0: bdf variant name not set.
[    3.726167] ath10k_pci 0000:05:00.0: boot using board name 
'bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000'
[    3.727652] ath10k_pci 0000:05:00.0: boot fw request 
'ath10k/QCA6174/hw3.0/board-2.bin': 0
[    3.727653] ath10k_pci 0000:05:00.0: board name
[    3.727654] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727655] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727656] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727657] ath10k_pci 0000:05:00.0: 00000030: 3d 31 36 38 63 2c 73 
75 62 73 79 73 74 65 6d 2d  =168c,subsystem-
[    3.727658] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
33 33 34 65                 device=334e
[    3.727658] ath10k_pci 0000:05:00.0: board name
[    3.727659] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727660] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727661] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727661] ath10k_pci 0000:05:00.0: 00000030: 3d 31 36 38 63 2c 73 
75 62 73 79 73 74 65 6d 2d  =168c,subsystem-
[    3.727662] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
33 33 36 30                 device=3360
[    3.727663] ath10k_pci 0000:05:00.0: board name
[    3.727663] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727664] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727665] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727666] ath10k_pci 0000:05:00.0: 00000030: 3d 31 36 38 63 2c 73 
75 62 73 79 73 74 65 6d 2d  =168c,subsystem-
[    3.727666] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
33 33 36 32                 device=3362
[    3.727667] ath10k_pci 0000:05:00.0: board name
[    3.727668] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727668] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727669] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727670] ath10k_pci 0000:05:00.0: 00000030: 3d 31 36 38 63 2c 73 
75 62 73 79 73 74 65 6d 2d  =168c,subsystem-
[    3.727670] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
33 33 36 33                 device=3363
[    3.727671] ath10k_pci 0000:05:00.0: board name
[    3.727672] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727672] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727673] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727674] ath10k_pci 0000:05:00.0: 00000030: 3d 31 36 38 63 2c 73 
75 62 73 79 73 74 65 6d 2d  =168c,subsystem-
[    3.727675] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
33 33 36 31                 device=3361
[    3.727675] ath10k_pci 0000:05:00.0: board name
[    3.727676] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727677] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727677] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727678] ath10k_pci 0000:05:00.0: 00000030: 3d 31 61 35 36 2c 73 
75 62 73 79 73 74 65 6d 2d  =1a56,subsystem-
[    3.727679] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
35 32 35 61                 device=525a
[    3.727680] ath10k_pci 0000:05:00.0: board name
[    3.727680] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727681] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727682] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727682] ath10k_pci 0000:05:00.0: 00000030: 3d 31 34 34 66 2c 73 
75 62 73 79 73 74 65 6d 2d  =144f,subsystem-
[    3.727683] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
37 31 34 33                 device=7143
[    3.727684] ath10k_pci 0000:05:00.0: board name
[    3.727684] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727685] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727686] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727687] ath10k_pci 0000:05:00.0: 00000030: 3d 31 36 38 63 2c 73 
75 62 73 79 73 74 65 6d 2d  =168c,subsystem-
[    3.727687] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
33 33 36 36                 device=3366
[    3.727688] ath10k_pci 0000:05:00.0: board name
[    3.727689] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727689] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727690] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727691] ath10k_pci 0000:05:00.0: 00000030: 3d 31 34 63 64 2c 73 
75 62 73 79 73 74 65 6d 2d  =14cd,subsystem-
[    3.727692] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
39 30 30 38                 device=9008
[    3.727692] ath10k_pci 0000:05:00.0: board name
[    3.727693] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727694] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727694] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727695] ath10k_pci 0000:05:00.0: 00000030: 3d 31 34 63 64 2c 73 
75 62 73 79 73 74 65 6d 2d  =14cd,subsystem-
[    3.727696] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
39 38 30 31                 device=9801
[    3.727696] ath10k_pci 0000:05:00.0: board name
[    3.727697] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727698] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727699] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727699] ath10k_pci 0000:05:00.0: 00000030: 3d 31 34 63 64 2c 73 
75 62 73 79 73 74 65 6d 2d  =14cd,subsystem-
[    3.727700] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
39 38 30 32                 device=9802
[    3.727701] ath10k_pci 0000:05:00.0: board name
[    3.727701] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727702] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727703] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727703] ath10k_pci 0000:05:00.0: 00000030: 3d 31 61 35 36 2c 73 
75 62 73 79 73 74 65 6d 2d  =1a56,subsystem-
[    3.727704] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
31 34 33 35                 device=1435
[    3.727705] ath10k_pci 0000:05:00.0: board name
[    3.727706] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727706] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727707] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727708] ath10k_pci 0000:05:00.0: 00000030: 3d 31 61 35 36 2c 73 
75 62 73 79 73 74 65 6d 2d  =1a56,subsystem-
[    3.727708] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
35 33 35 61                 device=535a
[    3.727709] ath10k_pci 0000:05:00.0: board name
[    3.727710] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727710] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727711] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727712] ath10k_pci 0000:05:00.0: 00000030: 3d 31 61 35 36 2c 73 
75 62 73 79 73 74 65 6d 2d  =1a56,subsystem-
[    3.727713] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
31 35 33 35                 device=1535
[    3.727713] ath10k_pci 0000:05:00.0: board name
[    3.727714] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727715] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727715] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727716] ath10k_pci 0000:05:00.0: 00000030: 3d 31 61 35 36 2c 73 
75 62 73 79 73 74 65 6d 2d  =1a56,subsystem-
[    3.727717] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
31 35 33 36                 device=1536
[    3.727717] ath10k_pci 0000:05:00.0: board name
[    3.727718] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727719] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727720] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727720] ath10k_pci 0000:05:00.0: 00000030: 3d 31 37 61 61 2c 73 
75 62 73 79 73 74 65 6d 2d  =17aa,subsystem-
[    3.727721] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
31 35 33 35                 device=1535
[    3.727722] ath10k_pci 0000:05:00.0: board name
[    3.727722] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727723] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727724] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727725] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 63 66 2c 73 
75 62 73 79 73 74 65 6d 2d  =10cf,subsystem-
[    3.727725] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
31 39 32 61                 device=192a
[    3.727726] ath10k_pci 0000:05:00.0: board name
[    3.727727] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727727] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727728] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727729] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 63 66 2c 73 
75 62 73 79 73 74 65 6d 2d  =10cf,subsystem-
[    3.727729] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
31 39 32 62                 device=192b
[    3.727730] ath10k_pci 0000:05:00.0: board name
[    3.727731] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727732] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727732] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727733] ath10k_pci 0000:05:00.0: 00000030: 3d 31 34 34 64 2c 73 
75 62 73 79 73 74 65 6d 2d  =144d,subsystem-
[    3.727734] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
34 31 32 66                 device=412f
[    3.727734] ath10k_pci 0000:05:00.0: board name
[    3.727735] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727736] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727736] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727737] ath10k_pci 0000:05:00.0: 00000030: 3d 31 34 34 64 2c 73 
75 62 73 79 73 74 65 6d 2d  =144d,subsystem-
[    3.727738] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
34 31 33 30                 device=4130
[    3.727739] ath10k_pci 0000:05:00.0: board name
[    3.727739] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727740] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727741] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727741] ath10k_pci 0000:05:00.0: 00000030: 3d 31 34 34 64 2c 73 
75 62 73 79 73 74 65 6d 2d  =144d,subsystem-
[    3.727742] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
34 31 33 31                 device=4131
[    3.727743] ath10k_pci 0000:05:00.0: board name
[    3.727743] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727744] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727745] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727746] ath10k_pci 0000:05:00.0: 00000030: 3d 31 34 34 64 2c 73 
75 62 73 79 73 74 65 6d 2d  =144d,subsystem-
[    3.727746] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
34 31 33 32                 device=4132
[    3.727747] ath10k_pci 0000:05:00.0: board name
[    3.727748] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727748] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727749] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727750] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 35 62 2c 73 
75 62 73 79 73 74 65 6d 2d  =105b,subsystem-
[    3.727751] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
65 30 61 30                 device=e0a0
[    3.727751] ath10k_pci 0000:05:00.0: board name
[    3.727752] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727753] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727753] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727754] ath10k_pci 0000:05:00.0: 00000030: 3d 31 31 61 64 2c 73 
75 62 73 79 73 74 65 6d 2d  =11ad,subsystem-
[    3.727755] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 35 30 33                 device=0503
[    3.727755] ath10k_pci 0000:05:00.0: board name
[    3.727756] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727757] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727758] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727758] ath10k_pci 0000:05:00.0: 00000030: 3d 31 31 61 64 2c 73 
75 62 73 79 73 74 65 6d 2d  =11ad,subsystem-
[    3.727759] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 38 30 37                 device=0807
[    3.727760] ath10k_pci 0000:05:00.0: board name
[    3.727760] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727761] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727762] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727762] ath10k_pci 0000:05:00.0: 00000030: 3d 31 31 61 64 2c 73 
75 62 73 79 73 74 65 6d 2d  =11ad,subsystem-
[    3.727763] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
31 38 30 37                 device=1807
[    3.727764] ath10k_pci 0000:05:00.0: board name
[    3.727765] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727765] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727766] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727767] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 35 62 2c 73 
75 62 73 79 73 74 65 6d 2d  =105b,subsystem-
[    3.727767] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
65 30 39 64                 device=e09d
[    3.727768] ath10k_pci 0000:05:00.0: board name
[    3.727769] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727769] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727770] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727771] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 34 33 2c 73 
75 62 73 79 73 74 65 6d 2d  =1043,subsystem-
[    3.727772] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
38 36 63 64                 device=86cd
[    3.727772] ath10k_pci 0000:05:00.0: board name
[    3.727773] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727774] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727774] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727775] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 34 33 2c 73 
75 62 73 79 73 74 65 6d 2d  =1043,subsystem-
[    3.727776] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
38 36 65 30                 device=86e0
[    3.727776] ath10k_pci 0000:05:00.0: board name
[    3.727777] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727778] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727779] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727779] ath10k_pci 0000:05:00.0: 00000030: 3d 31 61 33 62 2c 73 
75 62 73 79 73 74 65 6d 2d  =1a3b,subsystem-
[    3.727781] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
32 32 36 30                 device=2260
[    3.727781] ath10k_pci 0000:05:00.0: board name
[    3.727782] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727783] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727783] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727784] ath10k_pci 0000:05:00.0: 00000030: 3d 31 31 61 64 2c 73 
75 62 73 79 73 74 65 6d 2d  =11ad,subsystem-
[    3.727785] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 38 30 38                 device=0808
[    3.727785] ath10k_pci 0000:05:00.0: board name
[    3.727786] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727787] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727788] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727788] ath10k_pci 0000:05:00.0: 00000030: 3d 31 34 34 66 2c 73 
75 62 73 79 73 74 65 6d 2d  =144f,subsystem-
[    3.727789] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
37 31 34 34                 device=7144
[    3.727790] ath10k_pci 0000:05:00.0: board name
[    3.727790] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727791] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727792] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727792] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 34 33 2c 73 
75 62 73 79 73 74 65 6d 2d  =1043,subsystem-
[    3.727793] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
38 36 66 38                 device=86f8
[    3.727794] ath10k_pci 0000:05:00.0: board name
[    3.727794] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727795] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727796] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727797] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 34 33 2c 73 
75 62 73 79 73 74 65 6d 2d  =1043,subsystem-
[    3.727797] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
38 36 66 39                 device=86f9
[    3.727798] ath10k_pci 0000:05:00.0: board name
[    3.727799] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727799] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727800] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727801] ath10k_pci 0000:05:00.0: 00000030: 3d 31 37 61 61 2c 73 
75 62 73 79 73 74 65 6d 2d  =17aa,subsystem-
[    3.727802] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 38 32 37                 device=0827
[    3.727802] ath10k_pci 0000:05:00.0: board name
[    3.727803] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727804] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727804] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727805] ath10k_pci 0000:05:00.0: 00000030: 3d 31 37 61 61 2c 73 
75 62 73 79 73 74 65 6d 2d  =17aa,subsystem-
[    3.727806] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 38 33 37                 device=0837
[    3.727806] ath10k_pci 0000:05:00.0: board name
[    3.727807] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727808] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727809] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727809] ath10k_pci 0000:05:00.0: 00000030: 3d 31 37 61 61 2c 73 
75 62 73 79 73 74 65 6d 2d  =17aa,subsystem-
[    3.727810] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 38 34 37                 device=0847
[    3.727811] ath10k_pci 0000:05:00.0: board name
[    3.727811] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727812] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727813] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727813] ath10k_pci 0000:05:00.0: 00000030: 3d 31 37 61 61 2c 73 
75 62 73 79 73 74 65 6d 2d  =17aa,subsystem-
[    3.727814] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 38 35 37                 device=0857
[    3.727815] ath10k_pci 0000:05:00.0: board name
[    3.727816] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727816] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727817] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727818] ath10k_pci 0000:05:00.0: 00000030: 3d 31 37 61 61 2c 73 
75 62 73 79 73 74 65 6d 2d  =17aa,subsystem-
[    3.727818] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
31 34 33 35                 device=1435
[    3.727819] ath10k_pci 0000:05:00.0: board name
[    3.727820] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727820] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727821] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727822] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 32 38 2c 73 
75 62 73 79 73 74 65 6d 2d  =1028,subsystem-
[    3.727823] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 33 31 30                 device=0310
[    3.727823] ath10k_pci 0000:05:00.0: board name
[    3.727824] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727825] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727825] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727826] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 32 38 2c 73 
75 62 73 79 73 74 65 6d 2d  =1028,subsystem-
[    3.727827] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 34 31 30                 device=0410
[    3.727827] ath10k_pci 0000:05:00.0: board name
[    3.727828] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727829] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727830] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727830] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 32 38 2c 73 
75 62 73 79 73 74 65 6d 2d  =1028,subsystem-
[    3.727831] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 33 31 30 2c 76 61 72 69  device=0310,vari
[    3.727832] ath10k_pci 0000:05:00.0: 00000050: 61 6e 74 3d 52 56 5f 
30 35 31 39                 ant=RV_0519
[    3.727832] ath10k_pci 0000:05:00.0: board name
[    3.727833] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727834] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727834] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727835] ath10k_pci 0000:05:00.0: 00000030: 3d 31 61 35 36 2c 73 
75 62 73 79 73 74 65 6d 2d  =1a56,subsystem-
[    3.727836] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
31 35 33 35 2c 76 61 72 69  device=1535,vari
[    3.727837] ath10k_pci 0000:05:00.0: 00000050: 61 6e 74 3d 52 56 5f 
30 35 31 39                 ant=RV_0519
[    3.727837] ath10k_pci 0000:05:00.0: board name
[    3.727838] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727839] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727839] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727840] ath10k_pci 0000:05:00.0: 00000030: 3d 31 61 35 36 2c 73 
75 62 73 79 73 74 65 6d 2d  =1a56,subsystem-
[    3.727841] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
31 35 33 35 2c 76 61 72 69  device=1535,vari
[    3.727841] ath10k_pci 0000:05:00.0: 00000050: 61 6e 74 3d 52 56 5f 
30 35 32 30                 ant=RV_0520
[    3.727842] ath10k_pci 0000:05:00.0: board name
[    3.727843] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727843] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727844] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727845] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 35 62 2c 73 
75 62 73 79 73 74 65 6d 2d  =105b,subsystem-
[    3.727846] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
65 30 61 35                 device=e0a5
[    3.727846] ath10k_pci 0000:05:00.0: board name
[    3.727847] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727848] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727848] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727849] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 34 33 2c 73 
75 62 73 79 73 74 65 6d 2d  =1043,subsystem-
[    3.727850] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
38 37 35 31                 device=8751
[    3.727850] ath10k_pci 0000:05:00.0: board name
[    3.727851] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727852] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727853] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727853] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 34 33 2c 73 
75 62 73 79 73 74 65 6d 2d  =1043,subsystem-
[    3.727854] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
38 37 35 32                 device=8752
[    3.727855] ath10k_pci 0000:05:00.0: board name
[    3.727855] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727856] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727857] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727858] ath10k_pci 0000:05:00.0: 00000030: 3d 31 31 61 64 2c 73 
75 62 73 79 73 74 65 6d 2d  =11ad,subsystem-
[    3.727858] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 35 32 33                 device=0523
[    3.727859] ath10k_pci 0000:05:00.0: board name
[    3.727860] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727860] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727861] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727862] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 35 62 2c 73 
75 62 73 79 73 74 65 6d 2d  =105b,subsystem-
[    3.727862] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
65 30 61 32                 device=e0a2
[    3.727863] ath10k_pci 0000:05:00.0: board name
[    3.727864] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727865] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727865] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727866] ath10k_pci 0000:05:00.0: 00000030: 3d 31 31 61 64 2c 73 
75 62 73 79 73 74 65 6d 2d  =11ad,subsystem-
[    3.727867] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 38 33 37                 device=0837
[    3.727867] ath10k_pci 0000:05:00.0: board name
[    3.727868] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727869] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727869] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727870] ath10k_pci 0000:05:00.0: 00000030: 3d 31 64 61 63 2c 73 
75 62 73 79 73 74 65 6d 2d  =1dac,subsystem-
[    3.727871] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 32 35 38                 device=0258
[    3.727871] ath10k_pci 0000:05:00.0: board name
[    3.727872] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727873] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727874] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727874] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 35 62 2c 73 
75 62 73 79 73 74 65 6d 2d  =105b,subsystem-
[    3.727875] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
65 30 61 36                 device=e0a6
[    3.727876] ath10k_pci 0000:05:00.0: board name
[    3.727876] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727877] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727878] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727879] ath10k_pci 0000:05:00.0: 00000030: 3d 31 31 61 64 2c 73 
75 62 73 79 73 74 65 6d 2d  =11ad,subsystem-
[    3.727879] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 38 31 38                 device=0818
[    3.727880] ath10k_pci 0000:05:00.0: board name
[    3.727881] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727881] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727882] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727883] ath10k_pci 0000:05:00.0: 00000030: 3d 31 64 61 63 2c 73 
75 62 73 79 73 74 65 6d 2d  =1dac,subsystem-
[    3.727883] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 32 35 39                 device=0259
[    3.727884] ath10k_pci 0000:05:00.0: board name
[    3.727885] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727886] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727886] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727887] ath10k_pci 0000:05:00.0: 00000030: 3d 31 64 61 63 2c 73 
75 62 73 79 73 74 65 6d 2d  =1dac,subsystem-
[    3.727888] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 32 36 31                 device=0261
[    3.727888] ath10k_pci 0000:05:00.0: board name
[    3.727889] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727890] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727890] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727891] ath10k_pci 0000:05:00.0: 00000030: 3d 31 37 61 61 2c 73 
75 62 73 79 73 74 65 6d 2d  =17aa,subsystem-
[    3.727892] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
33 30 32 34                 device=3024
[    3.727893] ath10k_pci 0000:05:00.0: board name
[    3.727893] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727894] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727895] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727895] ath10k_pci 0000:05:00.0: 00000030: 3d 31 31 61 64 2c 73 
75 62 73 79 73 74 65 6d 2d  =11ad,subsystem-
[    3.727896] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
30 35 31 33                 device=0513
[    3.727897] ath10k_pci 0000:05:00.0: board name
[    3.727897] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727898] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727899] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727900] ath10k_pci 0000:05:00.0: 00000030: 3d 31 61 35 36 2c 73 
75 62 73 79 73 74 65 6d 2d  =1a56,subsystem-
[    3.727900] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
31 34 33 61                 device=143a
[    3.727901] ath10k_pci 0000:05:00.0: board name
[    3.727902] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727902] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727903] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727904] ath10k_pci 0000:05:00.0: 00000030: 3d 31 30 32 38 2c 73 
75 62 73 79 73 74 65 6d 2d  =1028,subsystem-
[    3.727905] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
33 36 34 61 2c 76 61 72 69  device=364a,vari
[    3.727905] ath10k_pci 0000:05:00.0: 00000050: 61 6e 74 3d 44 45 5f 
30 35 32 32                 ant=DE_0522
[    3.727906] ath10k_pci 0000:05:00.0: board name
[    3.727907] ath10k_pci 0000:05:00.0: 00000000: 62 75 73 3d 70 63 69 
2c 76 65 6e 64 6f 72 3d 31  bus=pci,vendor=1
[    3.727907] ath10k_pci 0000:05:00.0: 00000010: 36 38 63 2c 64 65 76 
69 63 65 3d 30 30 33 65 2c  68c,device=003e,
[    3.727908] ath10k_pci 0000:05:00.0: 00000020: 73 75 62 73 79 73 74 
65 6d 2d 76 65 6e 64 6f 72  subsystem-vendor
[    3.727909] ath10k_pci 0000:05:00.0: 00000030: 3d 31 61 35 36 2c 73 
75 62 73 79 73 74 65 6d 2d  =1a56,subsystem-
[    3.727909] ath10k_pci 0000:05:00.0: 00000040: 64 65 76 69 63 65 3d 
35 33 35 62                 device=535b
[    3.727911] ath10k_pci 0000:05:00.0: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000 
from ath10k/QCA6174/hw3.0/board-2.bin
[    3.728168] ath10k_pci 0000:05:00.0: boot fw request 
'ath10k/QCA6174/hw3.0/board.bin': 0
[    3.728169] ath10k_pci 0000:05:00.0: using board api 1
[    3.728177] ath10k_pci 0000:05:00.0: board_file api 1 bmi_id N/A 
crc32 ed5f849a
[    3.729100] ath10k_pci 0000:05:00.0: boot did not find a pre 
calibration file, try DT next: -2
[    3.729101] ath10k_pci 0000:05:00.0: unable to load pre cal data from 
DT: -2
[    3.729101] ath10k_pci 0000:05:00.0: failed to load pre cal data: -2
[    3.729102] ath10k_pci 0000:05:00.0: pre cal download procedure 
failed, try cal file: -2
[    3.729103] ath10k_pci 0000:05:00.0: boot did not find a calibration 
file, try DT next: -2
[    3.729103] ath10k_pci 0000:05:00.0: boot did not find DT entry, try 
target EEPROM next: -2
[    3.729104] ath10k_pci 0000:05:00.0: boot did not find target EEPROM 
entry, try OTP next: -95
[    3.729123] ath10k_pci 0000:05:00.0: boot push board extended data 
addr 0x0
[    3.734442] ath10k_pci 0000:05:00.0: boot upload otp to 0x1234 len 24193
[    3.751164] ath10k_pci 0000:05:00.0: boot otp execute result 2
[    3.751166] ath10k_pci 0000:05:00.0: boot using calibration mode otp
[    3.751167] ath10k_pci 0000:05:00.0: boot uploading firmware image 
ffffb2cc02227ed4 len 703151
[    4.291417] ath10k_pci 0000:05:00.0: boot htc service 'Control' ul 
pipe 0 dl pipe 1 eid 0 ready
[    4.291418] ath10k_pci 0000:05:00.0: boot htc service 'Control' eid 0 
TX flow control disabled
[    4.291427] ath10k_pci 0000:05:00.0: htt tx max num pending tx 1056
[    4.291434] ath10k_pci 0000:05:00.0: htt rx ring size 2048 fill_level 
1023
[    4.291435] ath10k_pci 0000:05:00.0: boot hif start
[    4.304531] ath10k_pci 0000:05:00.0: boot htc service HTT Data does 
not allocate target credits
[    4.304575] ath10k_pci 0000:05:00.0: boot htc service 'HTT Data' ul 
pipe 4 dl pipe 1 eid 1 ready
[    4.304576] ath10k_pci 0000:05:00.0: boot htc service 'HTT Data' eid 
1 TX flow control disabled
[    4.304607] ath10k_pci 0000:05:00.0: boot htc service 'WMI' ul pipe 3 
dl pipe 2 eid 2 ready
[    4.304878] ath10k_pci 0000:05:00.0: firmware 
WLAN.RM.4.4.1-00026-QCARMSWP-1 booted
[    4.319531] ath10k_pci 0000:05:00.0: Unknown eventid: 118809
[    4.322438] ath10k_pci 0000:05:00.0: Unknown eventid: 90118
[    4.323090] ath10k_pci 0000:05:00.0: htt target version 3.44
[    4.323096] ath10k_pci 0000:05:00.0: htt-ver 3.44 wmi-op 4 htt-op 3 
cal otp max-sta 32 raw 0 hwcrypto 1
[   10.716831] ath10k_pci 0000:05:00.0: could not suspend target (-11)
[   10.716834] ath10k_pci 0000:05:00.0: boot hif stop
[   10.716835] ath10k_pci 0000:05:00.0: boot warm reset
[   10.750133] ath10k_pci 0000:05:00.0: boot init ce src ring id 0 
entries 16 base_addr ffff9fcdf703e000
[   10.750142] ath10k_pci 0000:05:00.0: boot ce dest ring id 1 entries 
512 base_addr ffff9fcdf705e000
[   10.750151] ath10k_pci 0000:05:00.0: boot ce dest ring id 2 entries 
128 base_addr ffff9fcdf703f000
[   10.750161] ath10k_pci 0000:05:00.0: boot init ce src ring id 3 
entries 32 base_addr ffff9fcdf7040000
[   10.750174] ath10k_pci 0000:05:00.0: boot init ce src ring id 4 
entries 8192 base_addr ffff9fcdf7060000
[   10.750184] ath10k_pci 0000:05:00.0: boot init ce src ring id 7 
entries 2 base_addr ffff9fcdf7041000
[   10.750192] ath10k_pci 0000:05:00.0: boot ce dest ring id 7 entries 2 
base_addr ffff9fcdf7042000
[   10.750193] ath10k_pci 0000:05:00.0: boot waiting target to initialise
[   10.750195] ath10k_pci 0000:05:00.0: boot target indicator 0
[   10.760206] ath10k_pci 0000:05:00.0: boot target indicator 2
[   10.760212] ath10k_pci 0000:05:00.0: boot target initialised
[   10.776805] ath10k_pci 0000:05:00.0: boot init ce src ring id 0 
entries 16 base_addr ffff9fcdf703e000
[   10.776819] ath10k_pci 0000:05:00.0: boot ce dest ring id 1 entries 
512 base_addr ffff9fcdf705e000
[   10.776831] ath10k_pci 0000:05:00.0: boot ce dest ring id 2 entries 
128 base_addr ffff9fcdf703f000
[   10.776846] ath10k_pci 0000:05:00.0: boot init ce src ring id 3 
entries 32 base_addr ffff9fcdf7040000
[   10.776862] ath10k_pci 0000:05:00.0: boot init ce src ring id 4 
entries 8192 base_addr ffff9fcdf7060000
[   10.776877] ath10k_pci 0000:05:00.0: boot init ce src ring id 7 
entries 2 base_addr ffff9fcdf7041000
[   10.776889] ath10k_pci 0000:05:00.0: boot ce dest ring id 7 entries 2 
base_addr ffff9fcdf7042000
[   10.776890] ath10k_pci 0000:05:00.0: boot waiting target to initialise
[   10.776893] ath10k_pci 0000:05:00.0: boot target indicator 0
[   10.786902] ath10k_pci 0000:05:00.0: boot target indicator 2
[   10.786909] ath10k_pci 0000:05:00.0: boot target initialised
[   10.786909] ath10k_pci 0000:05:00.0: boot warm reset complete
[   10.787814] ath10k_pci 0000:05:00.0: boot hif power down
[   10.787922] ath10k_pci 0000:05:00.0: regulatory hint from WRDD 
(alpha2-code): AP
[   10.787923] ath10k_pci 0000:05:00.0: fallback to eeprom programmed 
regulatory settings
[   10.795609] ath10k_pci 0000:05:00.0 wlp5s0: renamed from wlan0

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: failed to fetch board data QCA6174
  2017-09-12  7:24   ` Luka Karinja
@ 2017-09-12  7:39     ` Luka Karinja
  2017-09-12 23:14     ` Ryan Hsu
  1 sibling, 0 replies; 16+ messages in thread
From: Luka Karinja @ 2017-09-12  7:39 UTC (permalink / raw)
  To: Ryan Hsu, ath10k@lists.infradead.org


On 09/12/2017 09:24 AM, Luka Karinja wrote:
>
>
> On 09/12/2017 12:25 AM, Ryan Hsu wrote:
>> On 09/11/2017 03:03 PM, Luka Karinja wrote:
>>
>>>>> Hello. I'm trying to get a M.2 QCA6174 working on my MSI 
>>>>> B150Mortar motherboard. i did try all the various firmware 
>>>>> versions from https://github.com/kvalo/ath10k-firmware more or 
>>>>> less with the same errors as bellow
>>>>>
>>>>> in dmesg i get: failed to fetch board data for 
>>>>> bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000 
>>>>> from ath10k/QCA6174/hw3.0/board-2.bin
>>>>>
>>>>> when trying to get the device up i get: RTNETLINK answers: 
>>>>> Resource temporarily unavailable
>>>>>
>>>>> [ 2026.219245] ath10k_pci 0000:05:00.0: pci irq msi oper_irq_mode 
>>>>> 2 irq_mode 0 reset_mode 0
>>>>> [ 2026.477510] ath10k_pci 0000:05:00.0: qca6174 hw3.2 target 
>>>>> 0x05030000 chip_id 0x00340aff sub 0000:0000
>>>>> [ 2026.477517] ath10k_pci 0000:05:00.0: kconfig debug 0 debugfs 1 
>>>>> tracing 0 dfs 0 testmode 0
>>>>> [ 2026.478640] ath10k_pci 0000:05:00.0: firmware ver 
>>>>> WLAN.RM.4.4.1-00026-QCARMSWP-1 api 6 features 
>>>>> wowlan,ignore-otp,raw-mode crc32 7b90c3fc
>>>>> [ 2026.542196] ath10k_pci 0000:05:00.0: failed to fetch board data 
>>>>> for 
>>>>> bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000 
>>>>> from ath10k/QCA6174/hw3.0/board-2.bin
>>>>>
>>>> Not sure what kernel and driver do you have?
>>>>
>>>> This should already fix this case - 
>>>> https://patchwork.kernel.org/patch/9486941/
>>>>
>>> I have kernel 4.12.10 (Arch linux) i did try with ath10k 
>>> WLAN.RM.2.4, 4.4, 4.4.1 firmware
>>>
>> ok, then it should be happening, would you mind enable the 
>> ATH10K_DBG_BOOT and share logs?
>> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/debug
>>
> here is the log with ATH10K_DBG_BOOT

BTW. that log is from kernel 4.13.1 and FW 4.4.1

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: failed to fetch board data QCA6174
  2017-09-12  7:24   ` Luka Karinja
  2017-09-12  7:39     ` Luka Karinja
@ 2017-09-12 23:14     ` Ryan Hsu
  2017-09-13  0:15       ` Carsten Haitzler
                         ` (2 more replies)
  1 sibling, 3 replies; 16+ messages in thread
From: Ryan Hsu @ 2017-09-12 23:14 UTC (permalink / raw)
  To: Luka Karinja, ath10k@lists.infradead.org

On 09/12/2017 12:24 AM, Luka Karinja wrote:

> [    3.662941] ath10k_pci 0000:05:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 0000:0000 

Hmm, where did you get this module? it seems like this module is not calibrated or assigned a sub IDs information, that why it cause the failure, since incorrect board file will lead to the firmware crash.

You might want to contact your module provider to give you the correct board file (board.bin) and replace it under the same firmware folder for testing/developing.

-- 
Ryan Hsu

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: failed to fetch board data QCA6174
  2017-09-12 23:14     ` Ryan Hsu
@ 2017-09-13  0:15       ` Carsten Haitzler
  2017-09-13  5:06         ` Ryan Hsu
  2017-09-13  6:00       ` Luka Karinja
       [not found]       ` <8b76e913-1205-db34-915b-658fdc017afe@gmail.com>
  2 siblings, 1 reply; 16+ messages in thread
From: Carsten Haitzler @ 2017-09-13  0:15 UTC (permalink / raw)
  To: Ryan Hsu; +Cc: Luka Karinja, ath10k@lists.infradead.org

On Tue, 12 Sep 2017 23:14:33 +0000 Ryan Hsu <ryanhsu@qti.qualcomm.com> said:

> On 09/12/2017 12:24 AM, Luka Karinja wrote:
> 
> > [    3.662941] ath10k_pci 0000:05:00.0: qca6174 hw3.2 target 0x05030000
> > chip_id 0x00340aff sub 0000:0000 
> 
> Hmm, where did you get this module? it seems like this module is not
> calibrated or assigned a sub IDs information, that why it cause the failure,
> since incorrect board file will lead to the firmware crash.
> 
> You might want to contact your module provider to give you the correct board
> file (board.bin) and replace it under the same firmware folder for
> testing/developing.

I see similar/same issues on an actual product (not some module or dev board).
a new-ish laptop/tablet that runs windows out of the box. I sent mails to to
here and linux-wireless too with zero responses on information on what the
board bin file is and the firmware bin files and how they are created etc. as I
suspected the key to the issue is somewhere there.

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
Carsten Haitzler - raster@rasterman.com


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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: failed to fetch board data QCA6174
  2017-09-13  0:15       ` Carsten Haitzler
@ 2017-09-13  5:06         ` Ryan Hsu
  2017-09-13 12:56           ` Carsten Haitzler
  0 siblings, 1 reply; 16+ messages in thread
From: Ryan Hsu @ 2017-09-13  5:06 UTC (permalink / raw)
  To: Carsten Haitzler; +Cc: Luka Karinja, ath10k@lists.infradead.org

On 09/12/2017 05:15 PM, Carsten Haitzler wrote:

> On Tue, 12 Sep 2017 23:14:33 +0000 Ryan Hsu <ryanhsu@qti.qualcomm.com> said:
>
>> On 09/12/2017 12:24 AM, Luka Karinja wrote:
>>
>>> [    3.662941] ath10k_pci 0000:05:00.0: qca6174 hw3.2 target 0x05030000
>>> chip_id 0x00340aff sub 0000:0000 
>> Hmm, where did you get this module? it seems like this module is not
>> calibrated or assigned a sub IDs information, that why it cause the failure,
>> since incorrect board file will lead to the firmware crash.
>>
>> You might want to contact your module provider to give you the correct board
>> file (board.bin) and replace it under the same firmware folder for
>> testing/developing.
> I see similar/same issues on an actual product (not some module or dev board).
> a new-ish laptop/tablet that runs windows out of the box. I sent mails to to
> here and linux-wireless too with zero responses on information on what the
> board bin file is and the firmware bin files and how they are created etc. as I
> suspected the key to the issue is somewhere there.
>

Sorry that I overlooked your post earlier (was out during that time and didn't have time to catch up the backlog...)

Your case is different from Luka's, your device do have the id calibrated, just that it is not added to the board-2.bin.

[  124.524661] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 144d:c14f

Here are some general guidance you might want to find out the right board file if it failed at first place.

For you case, your board is calibrated, so from the failure logs, you coudl see above string - sub 144d:c14f, and then either your install package or you could seek the driver online, e.g this might work to your board.
https://drp.su/en/hwids/PCI%5CVEN_168C%26DEV_003E%26SUBSYS_C14F144D%26REV_32

And then extract the file you could see the PCI\VEN_168C&DEV_003E&SUBSYS_C14F144D&REV_32 is using "eeprom_ar6320_3p0_SS_720.bin", so if you could give it a try by renaming it to board.bin under your firmware folder.

And would be appreciated if you could feedback the result.

-- 
Ryan Hsu

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: failed to fetch board data QCA6174
  2017-09-13  5:06         ` Ryan Hsu
@ 2017-09-13 12:56           ` Carsten Haitzler
  2017-09-13 18:23             ` Ryan Hsu
  0 siblings, 1 reply; 16+ messages in thread
From: Carsten Haitzler @ 2017-09-13 12:56 UTC (permalink / raw)
  To: Ryan Hsu; +Cc: Luka Karinja, ath10k@lists.infradead.org

On Wed, 13 Sep 2017 05:06:41 +0000 Ryan Hsu <ryanhsu@qti.qualcomm.com> said:

> On 09/12/2017 05:15 PM, Carsten Haitzler wrote:
> 
> > On Tue, 12 Sep 2017 23:14:33 +0000 Ryan Hsu <ryanhsu@qti.qualcomm.com> said:
> >
> >> On 09/12/2017 12:24 AM, Luka Karinja wrote:
> >>
> >>> [    3.662941] ath10k_pci 0000:05:00.0: qca6174 hw3.2 target 0x05030000
> >>> chip_id 0x00340aff sub 0000:0000 
> >> Hmm, where did you get this module? it seems like this module is not
> >> calibrated or assigned a sub IDs information, that why it cause the
> >> failure, since incorrect board file will lead to the firmware crash.
> >>
> >> You might want to contact your module provider to give you the correct
> >> board file (board.bin) and replace it under the same firmware folder for
> >> testing/developing.
> > I see similar/same issues on an actual product (not some module or dev
> > board). a new-ish laptop/tablet that runs windows out of the box. I sent
> > mails to to here and linux-wireless too with zero responses on information
> > on what the board bin file is and the firmware bin files and how they are
> > created etc. as I suspected the key to the issue is somewhere there.
> >
> 
> Sorry that I overlooked your post earlier (was out during that time and
> didn't have time to catch up the backlog...)

No problems Ryan! Thanks for the reply.

> Your case is different from Luka's, your device do have the id calibrated,
> just that it is not added to the board-2.bin.
> 
> [  124.524661] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000
> chip_id 0x00340aff sub 144d:c14f
> 
> 
> Here are some general guidance you might want to find out the right board
> file if it failed at first place.
> 
> For you case, your board is calibrated, so from the failure logs, you coudl
> see above string - sub 144d:c14f, and then either your install package or you
> could seek the driver online, e.g this might work to your board.
> https://drp.su/en/hwids/PCI%5CVEN_168C%26DEV_003E%26SUBSYS_C14F144D%26REV_32
> 
> And then extract the file you could see the PCI
> \VEN_168C&DEV_003E&SUBSYS_C14F144D&REV_32 is using
> "eeprom_ar6320_3p0_SS_720.bin", so if you could give it a try by renaming it
> to board.bin under your firmware folder.
> 
> And would be appreciated if you could feedback the result.

Absolutely. Well ... my first port of call instead of teh above site/url was to
use the matching file in the Qualcomm windows driver directory i copied off
windows before nuking it.  same filename. eeprom_ar6320_3p0_SS_720.bin. also
there's eeprom_ar6320_3p0_SS_720_K.bin too. I tried both... and:

[  154.007574] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 144d:c14f
[  154.007577] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[  154.008207] ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6 features wowlan,ignore-otp crc32 4d458559
[  154.072786] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=144d,subsystem-device=c14f,variant=K from ath10k/QCA6174/hw3.0/board-2.bin
[  154.072807] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 ed5f849a
[  154.640347] ath10k_pci 0000:01:00.0: Unknown eventid: 90118
[  157.709005] ath10k_pci 0000:01:00.0: failed to ping firmware: -110
[  157.709019] ath10k_pci 0000:01:00.0: failed to reset rx filter: -110
[  157.782164] ath10k_pci 0000:01:00.0: could not init core (-110)
[  157.782206] ath10k_pci 0000:01:00.0: could not probe fw (-110)

and for the _K variant:

[  372.001685] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 144d:c14f
[  372.001687] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[  372.002098] ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6 features wowlan,ignore-otp crc32 4d458559
[  372.066672] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=144d,subsystem-device=c14f,variant=K from ath10k/QCA6174/hw3.0/board-2.bin
[  372.066691] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 ad2a5746
[  372.634622] ath10k_pci 0000:01:00.0: Unknown eventid: 90118
[  372.635466] ath10k_pci 0000:01:00.0: htt-ver 3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[  372.713216] ath: EEPROM regdomain: 0x5f
[  372.713218] ath: EEPROM indicates we should expect a direct regpair map
[  372.713218] ath: invalid regulatory domain/country code 0x5f
[  372.713219] ath: Invalid EEPROM contents
[  372.713223] ath10k_pci 0000:01:00.0: failed to initialise regulatory: -22
[  372.713225] ath10k_pci 0000:01:00.0: could not register to mac80211 (-22)

same thing. board.bin is small like the windows eeprom files, so it makes sense and works. trying the url above to download from instead... exact same story. checksum for board file is different, but everything else is the same:

[   40.135513] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 144d:c14f
[   40.135516] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[   40.136046] ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6 features wowlan,ignore-otp crc32 4d458559
[   40.200646] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=144d,subsystem-device=c14f,variant=K from ath10k/QCA6174/hw3.0/board-2.bin
[   40.200664] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 d0d18eef
[   40.769329] ath10k_pci 0000:01:00.0: Unknown eventid: 90118
[   40.769912] ath10k_pci 0000:01:00.0: htt-ver 3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[   40.846830] ath: EEPROM regdomain: 0x5f
[   40.846831] ath: EEPROM indicates we should expect a direct regpair map
[   40.846832] ath: invalid regulatory domain/country code 0x5f
[   40.846832] ath: Invalid EEPROM contents
[   40.846837] ath10k_pci 0000:01:00.0: failed to initialise regulatory: -22
[   40.846839] ath10k_pci 0000:01:00.0: could not register to mac80211 (-22)

How can I help? The OEM developers are all windows people, so discussing Linux driver needs/specifics with them will be a bit of a challenge. Is there something I can ask for or get for you? As I said in my first mail, I already checked on GPIO's possibly powering down the device etc. and verified with the board HW/Driver devs that it's powered up as desired. Without background on the chips themselves, which driver bin files do what on what chips is a bit of a mystery which I assume you have far better insight into... :)

So what can I do to help? P.S. Thanks very much for the help/response. :)

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
Carsten Haitzler - raster@rasterman.com


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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: failed to fetch board data QCA6174
  2017-09-13 12:56           ` Carsten Haitzler
@ 2017-09-13 18:23             ` Ryan Hsu
  2017-09-14  0:38               ` Carsten Haitzler
  0 siblings, 1 reply; 16+ messages in thread
From: Ryan Hsu @ 2017-09-13 18:23 UTC (permalink / raw)
  To: Carsten Haitzler; +Cc: Luka Karinja, ath10k@lists.infradead.org

On 09/13/2017 05:56 AM, Carsten Haitzler wrote:

> Absolutely. Well ... my first port of call instead of teh above site/url was to
> use the matching file in the Qualcomm windows driver directory i copied off
> windows before nuking it.  same filename. eeprom_ar6320_3p0_SS_720.bin. also
> there's eeprom_ar6320_3p0_SS_720_K.bin too. I tried both... and:
>
> [  154.007574] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 144d:c14f
> [  154.007577] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
> [  154.008207] ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6 features wowlan,ignore-otp crc32 4d458559
> [  154.072786] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=144d,subsystem-device=c14f,variant=K from ath10k/QCA6174/hw3.0/board-2.bin
> [  154.072807] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 ed5f849a
> [  154.640347] ath10k_pci 0000:01:00.0: Unknown eventid: 90118
> [  157.709005] ath10k_pci 0000:01:00.0: failed to ping firmware: -110
> [  157.709019] ath10k_pci 0000:01:00.0: failed to reset rx filter: -110
> [  157.782164] ath10k_pci 0000:01:00.0: could not init core (-110)
> [  157.782206] ath10k_pci 0000:01:00.0: could not probe fw (-110)

So that means the eeprom_ar6320_3p0_SS_720.bin is not the one then, thanks I overlooked the k variant, but thanks for trying that as well.

> and for the _K variant:
>
> [  372.001685] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 144d:c14f
> [  372.001687] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
> [  372.002098] ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6 features wowlan,ignore-otp crc32 4d458559
> [  372.066672] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=144d,subsystem-device=c14f,variant=K from ath10k/QCA6174/hw3.0/board-2.bin
> [  372.066691] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 ad2a5746
> [  372.634622] ath10k_pci 0000:01:00.0: Unknown eventid: 90118
> [  372.635466] ath10k_pci 0000:01:00.0: htt-ver 3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
> [  372.713216] ath: EEPROM regdomain: 0x5f
> [  372.713218] ath: EEPROM indicates we should expect a direct regpair map
> [  372.713218] ath: invalid regulatory domain/country code 0x5f
> [  372.713219] ath: Invalid EEPROM contents
> [  372.713223] ath10k_pci 0000:01:00.0: failed to initialise regulatory: -22
> [  372.713225] ath10k_pci 0000:01:00.0: could not register to mac80211 (-22)

So the _K variant board file seems to be the right one, the firmware is not crashing now.
But failed due to the unknown country code 0x5f.

Could you give it a try with this to see if that helped to bring it up your case?
it might not be the final solution but would appreciate if you could help to debug a little bit.

diff --git a/drivers/net/wireless/ath/regd_common.h b/drivers/net/wireless/ath/regd_common.h
index bdd2b4d..ef578bf 100644
--- a/drivers/net/wireless/ath/regd_common.h
+++ b/drivers/net/wireless/ath/regd_common.h
@@ -71,6 +71,7 @@ enum EnumRd {
        APL7_FCCA = 0x5C,
        APL8_WORLD = 0x5D,
        APL9_WORLD = 0x5E,
+       APL10_WORLD = 0x5F,
 
        WOR0_WORLD = 0x60,
        WOR1_WORLD = 0x61,
@@ -194,6 +195,7 @@ static struct reg_dmn_pair_mapping regDomainPairs[] = {
        {APL6_WORLD, CTL_ETSI, CTL_ETSI},
        {APL8_WORLD, CTL_ETSI, CTL_ETSI},
        {APL9_WORLD, CTL_ETSI, CTL_ETSI},
+       {APL10_WORLD, CTL_ETSI, CTL_ETSI},
 
        {APL3_FCCA, CTL_FCC, CTL_FCC},
        {APL7_FCCA, CTL_FCC, CTL_FCC},
@@ -410,7 +412,7 @@ static struct country_code_to_enum_rd allCountries[] = {
        {CTRY_JORDAN, ETSI2_WORLD, "JO"},
        {CTRY_KAZAKHSTAN, NULL1_WORLD, "KZ"},
        {CTRY_KOREA_NORTH, APL9_WORLD, "KP"},
-       {CTRY_KOREA_ROC, APL9_WORLD, "KR"},
+       {CTRY_KOREA_ROC, APL10_WORLD, "KR"},
        {CTRY_KOREA_ROC2, APL2_WORLD, "K2"},
        {CTRY_KOREA_ROC3, APL9_WORLD, "K3"},
        {CTRY_KUWAIT, ETSI3_WORLD, "KW"},

> same thing. board.bin is small like the windows eeprom files, so it makes sense and works. trying the url above to download from instead... exact same story. checksum for board file is different, but everything else is the same:
>
> [   40.135513] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 144d:c14f
> [   40.135516] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
> [   40.136046] ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6 features wowlan,ignore-otp crc32 4d458559
> [   40.200646] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=144d,subsystem-device=c14f,variant=K from ath10k/QCA6174/hw3.0/board-2.bin
> [   40.200664] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 d0d18eef
> [   40.769329] ath10k_pci 0000:01:00.0: Unknown eventid: 90118
> [   40.769912] ath10k_pci 0000:01:00.0: htt-ver 3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
> [   40.846830] ath: EEPROM regdomain: 0x5f
> [   40.846831] ath: EEPROM indicates we should expect a direct regpair map
> [   40.846832] ath: invalid regulatory domain/country code 0x5f
> [   40.846832] ath: Invalid EEPROM contents
> [   40.846837] ath10k_pci 0000:01:00.0: failed to initialise regulatory: -22
> [   40.846839] ath10k_pci 0000:01:00.0: could not register to mac80211 (-22)

Ok, this is the same case, which board file are you using?

> How can I help? The OEM developers are all windows people, so discussing Linux driver needs/specifics with them will be a bit of a challenge. Is there something I can ask for or get for you? As I said in my first mail, I already checked on GPIO's possibly powering down the device etc. and verified with the board HW/Driver devs that it's powered up as desired. Without background on the chips themselves, which driver bin files do what on what chips is a bit of a mystery which I assume you have far better insight into... :)
>
> So what can I do to help? P.S. Thanks very much for the help/response. :)
>

A rule of thumb is to reporting the unknown or failure board with logs and the model of your laptop, so that we could know what is failing.
Windows driver is a good reference of which firmware is good for your module, we don't need them to know the Linux driver itself, as this kind of case is mostly due to the mismatch firmware or board files, so if you've access to them, try to check what files you should be using, and then we could add that back to board-2.bin so that more user can benefit.

-- 
Ryan Hsu

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

^ permalink raw reply related	[flat|nested] 16+ messages in thread

* Re: failed to fetch board data QCA6174
  2017-09-13 18:23             ` Ryan Hsu
@ 2017-09-14  0:38               ` Carsten Haitzler
  0 siblings, 0 replies; 16+ messages in thread
From: Carsten Haitzler @ 2017-09-14  0:38 UTC (permalink / raw)
  To: Ryan Hsu; +Cc: Luka Karinja, ath10k@lists.infradead.org

On Wed, 13 Sep 2017 18:23:37 +0000 Ryan Hsu <ryanhsu@qti.qualcomm.com> said:

> On 09/13/2017 05:56 AM, Carsten Haitzler wrote:
> 
> > Absolutely. Well ... my first port of call instead of teh above site/url
> > was to use the matching file in the Qualcomm windows driver directory i
> > copied off windows before nuking it.  same filename.
> > eeprom_ar6320_3p0_SS_720.bin. also there's eeprom_ar6320_3p0_SS_720_K.bin
> > too. I tried both... and:
> >
> > [  154.007574] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000
> > chip_id 0x00340aff sub 144d:c14f [  154.007577] ath10k_pci 0000:01:00.0:
> > kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0 [  154.008207]
> > ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6
> > features wowlan,ignore-otp crc32 4d458559 [  154.072786] ath10k_pci
> > 0000:01:00.0: failed to fetch board data for
> > bus=pci,vendor=168c,device=003e,subsystem-vendor=144d,subsystem-device=c14f,variant=K
> > from ath10k/QCA6174/hw3.0/board-2.bin [  154.072807] ath10k_pci
> > 0000:01:00.0: board_file api 1 bmi_id N/A crc32 ed5f849a [  154.640347]
> > ath10k_pci 0000:01:00.0: Unknown eventid: 90118 [  157.709005] ath10k_pci
> > 0000:01:00.0: failed to ping firmware: -110 [  157.709019] ath10k_pci
> > 0000:01:00.0: failed to reset rx filter: -110 [  157.782164] ath10k_pci
> > 0000:01:00.0: could not init core (-110) [  157.782206] ath10k_pci
> > 0000:01:00.0: could not probe fw (-110)
> 
> So that means the eeprom_ar6320_3p0_SS_720.bin is not the one then, thanks I
> overlooked the k variant, but thanks for trying that as well.
> 
> > and for the _K variant:
> >
> > [  372.001685] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000
> > chip_id 0x00340aff sub 144d:c14f [  372.001687] ath10k_pci 0000:01:00.0:
> > kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0 [  372.002098]
> > ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6
> > features wowlan,ignore-otp crc32 4d458559 [  372.066672] ath10k_pci
> > 0000:01:00.0: failed to fetch board data for
> > bus=pci,vendor=168c,device=003e,subsystem-vendor=144d,subsystem-device=c14f,variant=K
> > from ath10k/QCA6174/hw3.0/board-2.bin [  372.066691] ath10k_pci
> > 0000:01:00.0: board_file api 1 bmi_id N/A crc32 ad2a5746 [  372.634622]
> > ath10k_pci 0000:01:00.0: Unknown eventid: 90118 [  372.635466] ath10k_pci
> > 0000:01:00.0: htt-ver 3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0
> > hwcrypto 1 [  372.713216] ath: EEPROM regdomain: 0x5f [  372.713218] ath:
> > EEPROM indicates we should expect a direct regpair map [  372.713218] ath:
> > invalid regulatory domain/country code 0x5f [  372.713219] ath: Invalid
> > EEPROM contents [  372.713223] ath10k_pci 0000:01:00.0: failed to
> > initialise regulatory: -22 [  372.713225] ath10k_pci 0000:01:00.0: could
> > not register to mac80211 (-22)
> 
> So the _K variant board file seems to be the right one, the firmware is not
> crashing now. But failed due to the unknown country code 0x5f.
> 
> Could you give it a try with this to see if that helped to bring it up your
> case? it might not be the final solution but would appreciate if you could
> help to debug a little bit.
> 
> diff --git a/drivers/net/wireless/ath/regd_common.h
> b/drivers/net/wireless/ath/regd_common.h index bdd2b4d..ef578bf 100644
> --- a/drivers/net/wireless/ath/regd_common.h
> +++ b/drivers/net/wireless/ath/regd_common.h
> @@ -71,6 +71,7 @@ enum EnumRd {
>         APL7_FCCA = 0x5C,
>         APL8_WORLD = 0x5D,
>         APL9_WORLD = 0x5E,
> +       APL10_WORLD = 0x5F,
>  
>         WOR0_WORLD = 0x60,
>         WOR1_WORLD = 0x61,
> @@ -194,6 +195,7 @@ static struct reg_dmn_pair_mapping regDomainPairs[] = {
>         {APL6_WORLD, CTL_ETSI, CTL_ETSI},
>         {APL8_WORLD, CTL_ETSI, CTL_ETSI},
>         {APL9_WORLD, CTL_ETSI, CTL_ETSI},
> +       {APL10_WORLD, CTL_ETSI, CTL_ETSI},
>  
>         {APL3_FCCA, CTL_FCC, CTL_FCC},
>         {APL7_FCCA, CTL_FCC, CTL_FCC},
> @@ -410,7 +412,7 @@ static struct country_code_to_enum_rd allCountries[] = {
>         {CTRY_JORDAN, ETSI2_WORLD, "JO"},
>         {CTRY_KAZAKHSTAN, NULL1_WORLD, "KZ"},
>         {CTRY_KOREA_NORTH, APL9_WORLD, "KP"},
> -       {CTRY_KOREA_ROC, APL9_WORLD, "KR"},
> +       {CTRY_KOREA_ROC, APL10_WORLD, "KR"},
>         {CTRY_KOREA_ROC2, APL2_WORLD, "K2"},
>         {CTRY_KOREA_ROC3, APL9_WORLD, "K3"},
>         {CTRY_KUWAIT, ETSI3_WORLD, "KW"},

applied against 4.13.0 ... and using the above K board bin variant... and we're
working! wifi is up... it's even stable... seemingly. (i can rsync happily etc.
right now. ssh interactive shell working). so for now.. i declare this bug
"fixed".

now comes step 2. the above patch obviously solves the source side of things.
you'll need to somehow merge the standard linux kernel firmware board.bin with
this one to make it work. i still get:

[    3.371736] ath10k_pci 0000:01:00.0: failed to fetch board data for
bus=pci,vendor=168c,device=003e,subsystem-vendor=144d,subsystem-device=c14f,variant=K
from ath10k/QCA6174/hw3.0/board-2.bin

and:

[    3.939978] ath10k_pci 0000:01:00.0: Unknown eventid: 90118

but for now they seem harmless to things working.

> > same thing. board.bin is small like the windows eeprom files, so it makes
> > sense and works. trying the url above to download from instead... exact
> > same story. checksum for board file is different, but everything else is
> > the same:
> >
> > [   40.135513] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000
> > chip_id 0x00340aff sub 144d:c14f [   40.135516] ath10k_pci 0000:01:00.0:
> > kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0 [   40.136046]
> > ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6
> > features wowlan,ignore-otp crc32 4d458559 [   40.200646] ath10k_pci
> > 0000:01:00.0: failed to fetch board data for
> > bus=pci,vendor=168c,device=003e,subsystem-vendor=144d,subsystem-device=c14f,variant=K
> > from ath10k/QCA6174/hw3.0/board-2.bin [   40.200664] ath10k_pci
> > 0000:01:00.0: board_file api 1 bmi_id N/A crc32 d0d18eef [   40.769329]
> > ath10k_pci 0000:01:00.0: Unknown eventid: 90118 [   40.769912] ath10k_pci
> > 0000:01:00.0: htt-ver 3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0
> > hwcrypto 1 [   40.846830] ath: EEPROM regdomain: 0x5f [   40.846831] ath:
> > EEPROM indicates we should expect a direct regpair map [   40.846832] ath:
> > invalid regulatory domain/country code 0x5f [   40.846832] ath: Invalid
> > EEPROM contents [   40.846837] ath10k_pci 0000:01:00.0: failed to
> > initialise regulatory: -22 [   40.846839] ath10k_pci 0000:01:00.0: could
> > not register to mac80211 (-22)
> 
> Ok, this is the same case, which board file are you using?

the k variant from the "driver download url" you provided.

> > How can I help? The OEM developers are all windows people, so discussing
> > Linux driver needs/specifics with them will be a bit of a challenge. Is
> > there something I can ask for or get for you? As I said in my first mail, I
> > already checked on GPIO's possibly powering down the device etc. and
> > verified with the board HW/Driver devs that it's powered up as desired.
> > Without background on the chips themselves, which driver bin files do what
> > on what chips is a bit of a mystery which I assume you have far better
> > insight into... :)
> >
> > So what can I do to help? P.S. Thanks very much for the help/response. :)
> >
> 
> A rule of thumb is to reporting the unknown or failure board with logs and
> the model of your laptop, so that we could know what is failing. Windows

It's brand shiny and new... Galaxy book 12 (i5, 8gb version ... that somewhere
also has LTE on board that i am not even going to have a hope in hell of making
it work). :) I also work for Samsung but the team that does this device is a
completely different one... but I can talk to them (and they helped me identify
the GPIO's i need). Thus why I say I can help with things that may need some
reverse engineering normally. But this looked like a firmware issue and the QCA
chip is a "3rd party" unit that I can't help with the internals of.

> driver is a good reference of which firmware is good for your module, we
> don't need them to know the Linux driver itself, as this kind of case is
> mostly due to the mismatch firmware or board files, so if you've access to
> them, try to check what files you should be using, and then we could add that
> back to board-2.bin so that more user can benefit.

Actually... no need for all of that. We've figured it out above. Fantastic. I
no longer need that horrible usb-c hub/dongle and usb wifi thing. Now I can
focus on my other issues to solve (backlight, headphones/speakers, touch
screen going nuts with spurious interrupts after unhibernate...
accelerometers, ...)

Do you need the board bin file?

> -- 
> Ryan Hsu
> 
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
> 


-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
Carsten Haitzler - raster@rasterman.com


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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: failed to fetch board data QCA6174
  2017-09-12 23:14     ` Ryan Hsu
  2017-09-13  0:15       ` Carsten Haitzler
@ 2017-09-13  6:00       ` Luka Karinja
       [not found]       ` <8b76e913-1205-db34-915b-658fdc017afe@gmail.com>
  2 siblings, 0 replies; 16+ messages in thread
From: Luka Karinja @ 2017-09-13  6:00 UTC (permalink / raw)
  To: Ryan Hsu, ath10k@lists.infradead.org


On 09/13/2017 01:14 AM, Ryan Hsu wrote:
> On 09/12/2017 12:24 AM, Luka Karinja wrote:
>
>> [    3.662941] ath10k_pci 0000:05:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 0000:0000
> Hmm, where did you get this module? it seems like this module is not calibrated or assigned a sub IDs information, that why it cause the failure, since incorrect board file will lead to the firmware crash.
>
> You might want to contact your module provider to give you the correct board file (board.bin) and replace it under the same firmware folder for testing/developing.
>

Hello. Its a module from ebay. So probably i can't do much with it 
without the right board.bin?

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

[parent not found: <8b76e913-1205-db34-915b-658fdc017afe@gmail.com>]

* Re: failed to fetch board data QCA6174
       [not found]       ` <8b76e913-1205-db34-915b-658fdc017afe@gmail.com>
@ 2017-09-13  7:00         ` Ryan Hsu
  2017-09-13 19:24           ` Luka Karinja
  0 siblings, 1 reply; 16+ messages in thread
From: Ryan Hsu @ 2017-09-13  7:00 UTC (permalink / raw)
  To: Luka Karinja, ath10k@lists.infradead.org

On 09/12/2017 10:59 PM, Luka Karinja wrote:

> Hello. Its a module from ebay. So probably i can't do much with it without the right board.bin?
>
> this is the module: http://www.ebay.com/itm/Qualcomm-Atheros-QCA6174-QCNFA344A-NGFF-M-2-WIFI-Card-BT4-1-WLAN-Wireless-Blueto/182599401035?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649#viTabs_0

Not sure would this works, can you please try to take the driver from here and extract the files.

https://drp.su/en/hwids/PCI%5CVEN_168C%26DEV_003E%26SUBSYS_C14F144D%26REV_32

From the inf, QCNFA344A likely is using eeprom_ar6320_3p0_NFA344a.bin (assumed is NFA364A equivalent), rename it to board.bin to see if that works?

-- 
Ryan Hsu

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: failed to fetch board data QCA6174
  2017-09-13  7:00         ` Ryan Hsu
@ 2017-09-13 19:24           ` Luka Karinja
  2017-09-13 22:14             ` Ryan Hsu
  0 siblings, 1 reply; 16+ messages in thread
From: Luka Karinja @ 2017-09-13 19:24 UTC (permalink / raw)
  To: Ryan Hsu, ath10k@lists.infradead.org

On 09/13/2017 09:00 AM, Ryan Hsu wrote:
> On 09/12/2017 10:59 PM, Luka Karinja wrote:
>
>> Hello. Its a module from ebay. So probably i can't do much with it without the right board.bin?
>>
>> this is the module: http://www.ebay.com/itm/Qualcomm-Atheros-QCA6174-QCNFA344A-NGFF-M-2-WIFI-Card-BT4-1-WLAN-Wireless-Blueto/182599401035?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649#viTabs_0
> Not sure would this works, can you please try to take the driver from here and extract the files.
>
> https://drp.su/en/hwids/PCI%5CVEN_168C%26DEV_003E%26SUBSYS_C14F144D%26REV_32
>
>  From the inf, QCNFA344A likely is using eeprom_ar6320_3p0_NFA344a.bin (assumed is NFA364A equivalent), rename it to board.bin to see if that works?
>
i did try:
eeprom_ar6320_3p0_NFA344a.bin
eeprom_ar6320_3p0_NFA344a_BLP.bin
eeprom_ar6320_3p0_NFA344A_power1213.bin
with the same calibration not found errors

so if i understand correctly, the only way to get it working is with 
manufacturers board.bin?

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: failed to fetch board data QCA6174
  2017-09-13 19:24           ` Luka Karinja
@ 2017-09-13 22:14             ` Ryan Hsu
  0 siblings, 0 replies; 16+ messages in thread
From: Ryan Hsu @ 2017-09-13 22:14 UTC (permalink / raw)
  To: Luka Karinja, ath10k@lists.infradead.org

On 09/13/2017 12:24 PM, Luka Karinja wrote:

> On 09/13/2017 09:00 AM, Ryan Hsu wrote:
> i did try:
> eeprom_ar6320_3p0_NFA344a.bin
> eeprom_ar6320_3p0_NFA344a_BLP.bin
> eeprom_ar6320_3p0_NFA344A_power1213.bin
> with the same calibration not found errors
>

Thanks for testing them out, glad it works.

> so if i understand correctly, the only way to get it working is with manufacturers board.bin?

Well, yes, so every boards have different characteristics, usually the manufacturer will know them and compile a board file that match to the module.
From this case, it is likely they're building the board, but didn't do the calibration, so that it failed to find the right board (either in board-2.bin or board.bin) file to load.

One note, even it is working to your board, but it might not the optimal case, as these are the general board file (e.g for NFA344A).
So if you need to run peak throughput testing it'll really need help from the manufacturer to provide or guide you to the right file for your module.

-- 
Ryan Hsu

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* failed to fetch board data QCA6174
@ 2017-09-11 16:54 Luka Karinja
  2017-09-11 21:15 ` Ryan Hsu
  0 siblings, 1 reply; 16+ messages in thread
From: Luka Karinja @ 2017-09-11 16:54 UTC (permalink / raw)
  To: ath10k

Hello. I'm trying to get a M.2 QCA6174 working on my MSI B150Mortar 
motherboard. i did try all the various firmware versions from 
https://github.com/kvalo/ath10k-firmware more or less with the same 
errors as bellow

in dmesg i get: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000 
from ath10k/QCA6174/hw3.0/board-2.bin

when trying to get the device up i get: RTNETLINK answers: Resource 
temporarily unavailable

[ 2026.219245] ath10k_pci 0000:05:00.0: pci irq msi oper_irq_mode 2 
irq_mode 0 reset_mode 0
[ 2026.477510] ath10k_pci 0000:05:00.0: qca6174 hw3.2 target 0x05030000 
chip_id 0x00340aff sub 0000:0000
[ 2026.477517] ath10k_pci 0000:05:00.0: kconfig debug 0 debugfs 1 
tracing 0 dfs 0 testmode 0
[ 2026.478640] ath10k_pci 0000:05:00.0: firmware ver 
WLAN.RM.4.4.1-00026-QCARMSWP-1 api 6 features wowlan,ignore-otp,raw-mode 
crc32 7b90c3fc
[ 2026.542196] ath10k_pci 0000:05:00.0: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000 
from ath10k/QCA6174/hw3.0/board-2.bin
[ 2026.542220] ath10k_pci 0000:05:00.0: board_file api 1 bmi_id N/A 
crc32 ed5f849a
[ 2027.117429] ath10k_pci 0000:05:00.0: Unknown eventid: 118809
[ 2027.120351] ath10k_pci 0000:05:00.0: Unknown eventid: 90118
[ 2027.121051] ath10k_pci 0000:05:00.0: htt-ver 3.44 wmi-op 4 htt-op 3 
cal otp max-sta 32 raw 0 hwcrypto 1
[ 2030.171942] ath10k_pci 0000:05:00.0: could not suspend target (-11)
[ 2030.243437] ath: EEPROM regdomain: 0x0
[ 2030.243441] ath: EEPROM indicates default country code should be used
[ 2030.243443] ath: doing EEPROM country->regdmn map search
[ 2030.243445] ath: country maps to regdmn code: 0x3a
[ 2030.243448] ath: Country alpha2 being used: US
[ 2030.243449] ath: Regpair used: 0x3a
[ 2030.252080] ath10k_pci 0000:05:00.0 wlp5s0: renamed from wlan0

when issuing: ip link set wlp5s0 up

[ 2105.582268] ath10k_pci 0000:05:00.0: Unknown eventid: 118809
[ 2105.585169] ath10k_pci 0000:05:00.0: Unknown eventid: 90118
[ 2108.676550] ath10k_pci 0000:05:00.0: failed to enable PMF QOS: -11
[ 2115.076644] ath10k_pci 0000:05:00.0: could not suspend target (-11)
[ 2118.097027] ath10k_pci 0000:05:00.0: Unknown eventid: 118809
[ 2118.099870] ath10k_pci 0000:05:00.0: Unknown eventid: 90118
[ 2121.263417] ath10k_pci 0000:05:00.0: failed to enable PMF QOS: -11
[ 2127.663515] ath10k_pci 0000:05:00.0: could not suspend target (-11)
[ 3171.741299] ath10k_pci 0000:05:00.0: Unknown eventid: 118809
[ 3171.744232] ath10k_pci 0000:05:00.0: Unknown eventid: 90118
[ 3174.937595] ath10k_pci 0000:05:00.0: failed to enable PMF QOS: -11
[ 3181.334350] ath10k_pci 0000:05:00.0: could not suspend target (-11)


lshw -C network

   *-network DISABLED
        description: Wireless interface
        product: QCA6174 802.11ac Wireless Network Adapter
        vendor: Qualcomm Atheros
        physical id: 0
        bus info: pci@0000:05:00.0
        logical name: wlp5s0
        version: 32
        serial: 00:03:7f:50:00:01
        width: 64 bits
        clock: 33MHz
        capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
        configuration: broadcast=yes driver=ath10k_pci 
driverversion=4.12.10-1-ARCH firmware=WLAN.RM.4.4.1-00026-QCARMSWP-1 
latency=0 link=no multicast=yes wireless=IEEE 802.11
        resources: irq:128 memory:df000000-df1fffff


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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: failed to fetch board data QCA6174
  2017-09-11 16:54 Luka Karinja
@ 2017-09-11 21:15 ` Ryan Hsu
  0 siblings, 0 replies; 16+ messages in thread
From: Ryan Hsu @ 2017-09-11 21:15 UTC (permalink / raw)
  To: ath10k@lists.infradead.org

On 09/11/2017 09:54 AM, Luka Karinja wrote:

> Hello. I'm trying to get a M.2 QCA6174 working on my MSI B150Mortar motherboard. i did try all the various firmware versions from https://github.com/kvalo/ath10k-firmware more or less with the same errors as bellow
>
> in dmesg i get: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000 from ath10k/QCA6174/hw3.0/board-2.bin
>
> when trying to get the device up i get: RTNETLINK answers: Resource temporarily unavailable
>
> [ 2026.219245] ath10k_pci 0000:05:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
> [ 2026.477510] ath10k_pci 0000:05:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 0000:0000
> [ 2026.477517] ath10k_pci 0000:05:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
> [ 2026.478640] ath10k_pci 0000:05:00.0: firmware ver WLAN.RM.4.4.1-00026-QCARMSWP-1 api 6 features wowlan,ignore-otp,raw-mode crc32 7b90c3fc
> [ 2026.542196] ath10k_pci 0000:05:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000 from ath10k/QCA6174/hw3.0/board-2.bin
>

Not sure what kernel and driver do you have?

This should already fix this case - https://patchwork.kernel.org/patch/9486941/

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

end of thread, other threads:[~2017-09-14  0:39 UTC | newest]

Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-09-11 22:03 failed to fetch board data QCA6174 Luka Karinja
2017-09-11 22:25 ` Ryan Hsu
2017-09-12  7:24   ` Luka Karinja
2017-09-12  7:39     ` Luka Karinja
2017-09-12 23:14     ` Ryan Hsu
2017-09-13  0:15       ` Carsten Haitzler
2017-09-13  5:06         ` Ryan Hsu
2017-09-13 12:56           ` Carsten Haitzler
2017-09-13 18:23             ` Ryan Hsu
2017-09-14  0:38               ` Carsten Haitzler
2017-09-13  6:00       ` Luka Karinja
     [not found]       ` <8b76e913-1205-db34-915b-658fdc017afe@gmail.com>
2017-09-13  7:00         ` Ryan Hsu
2017-09-13 19:24           ` Luka Karinja
2017-09-13 22:14             ` Ryan Hsu
  -- strict thread matches above, loose matches on Subject: below --
2017-09-11 16:54 Luka Karinja
2017-09-11 21:15 ` Ryan Hsu

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox