Oh, sorry, forgot to mention that.  It's a custom Intel-based platform (based 
on an Atom Rangeley reference design, with a PCIe Ath10k card from Compex, 
based on a QCA9880).

> On Apr 7, 2015, at 12:13 PM, Irfan Zia <[email protected]> wrote:
> 
> 
> Which platform ?  Is it a TP-Link device ?  We did some recent work on  
> Archer c7v2. &  DB-120(WDR4300)
> 
> -Irfan
> Paxym Inc.
> www.paxym.com <http://www.paxym.com/>
> 
> 
> On Tue, Apr 7, 2015 at 11:34 AM, Shankar Unni <[email protected] 
> <mailto:[email protected]>> wrote:
> We have an openwrt build that we're working with, that has the most recent 
> compat-wireless from the trunk (package/kernel/mac80211).
> 
> When we load the ath10k driver, it seems to pause for several seconds and 
> write out a message about not finding a particular firmware file:
> 
> [    6.418730] ath10k_pci 0000:01:00.0: pci irq msi interrupts 1 irq_mode 0 
> reset_mode 0
> [    6.548286] ath10k_pci 0000:01:00.0: Direct firmware load failed with 
> error -2
> [    6.555670] ath10k_pci 0000:01:00.0: Falling back to user helper
> procd: Could not find firmware /lib/firmware/ath10k/cal-pci-0000:01:00.0.bin
> [   13.546479] ath10k_pci 0000:01:00.0: qca988x hw2.0 (0x4100016c, 
> 0x043202ff) fw 10.2.4.45 api 4 htt 2.1 wmi 5 cal otp max_sta 128
> [   13.558583] ath10k_pci 0000:01:00.0: no channel configured; ignoring 
> frame(s)!
> [   13.566102] ath10k_pci 0000:01:00.0: debug 0 debugfs 1 tracing 0 dfs 1 
> testmode 1
> [   13.566109] ath10k_pci 0000:01:00.0: no channel configured; ignoring 
> frame(s)!
> 
> And of course, there is no such file 
> (/lib/firmware/ath10k/cal-pci-0000:01:00.0.bin). Where do we get this file 
> from (or how do we create it)? Is this something I should be worried about?  
> Also, what's this direct firmware load message? Is that for the same file 
> (I'm expecting so).
> 
> Also, the 7 second pause.  But that, I guess, is because the ath10k driver 
> load is now synchronous, right?
> 
> Finally, should I worry about the "no channel configured; ignoring frame(s)" 
> message? It gets emitted several times at driver load time, but stops after 
> that.
> _______________________________________________
> openwrt-devel mailing list
> [email protected] <mailto:[email protected]>
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel 
> <https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel>
> 

_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to