On 2017-11-21 01:13, Matthew McClintock wrote:
I think it's complaining that it can't find the right board info from
the board-2.bin file which is just multiple board files wrapped up
together?
[ 233.761660] ath10k_ahb a000000.wifi: failed to fetch board data
for
bus=ahb,vendor=0000,device=0000,subsystem-vendor=0000,subsystem-device=0000
from ath10k/QCA4019/hw1.0/board-2.bin
The device identifcation doesn't work.
The driver is thinking it has a non-sensical "ahb pci(e)" device.
Just look at the fact that the driver is looking for "bus=ahb" but
also
"vendor=0,device=0...,subsystem...=...,..."(which is used to identify
pcie devices). If it was looking for a bmi device, the board search
string
would look something like "bus=ahb,bmi-chip-id=0,bmi-board-id=16"
I think this is the root of the problem.
I can only guess what's really going on, since this is such a short
extract.
But there at least two likely scenarios:
1. 936-ath10k_skip_otp_check.patch is present / ath10k is too old
This is not present.
2. the pre-cal-ahb-a800000.wifi.bin and pre-cal-ahb-a000000.wifi.bin
don't get loaded or the pre-cal* data is
shifted/trimmed/mangled/bad.
For 2. you should check if the firmware hotplug 11-ath10k-caldata
script
is correctly extracting the pre-cal from the "ART" Partition of your
device
I would first look at this ^^^
Regards,
Roman
_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
