compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2

[Michal Kazior]

On 12 June 2014 21:37, Sven Schnelle <svens at stackframe.org> wrote:
> Am 12.06.2014 14:57, schrieb Michal Kazior:
>> Interesting. I assume you see this exact same mac addr in ifconfig for
>> ath10k's wlan interface? If OTP is broken you usually get 00:03:07:12:34:56
>> if my memory serves right. What mac address do you get when you use the
>> stock firmware-2.bin and board.bin (instead of mine/from mtd)? Michał
>
>
> I get the mac address from board.bin. If i understand OTP correct, it should
> instead use the Mac Adress from
> OTP. My guess is that the OTP Memory on that device is simply not
> programmed, so it falls back to board.bin.
> Is my assumption correct? On system without programmed OTP, shouldn't ath10k
> start up and simply fall back
> to board.bin instead of bailing out?
>
> I'm not sure if i really unterstood how otp and board.bin relates to each
> other now. ;)

>From what I understand board.bin is required by otp.bin. board.bin
seems like data while otp.bin is a program that is executed on the
device.

It might be that otp.bin falls back to board.bin or maybe uses
board.bin as a bootstrap of sorts (e.g. points to a custom location
where otp data is actually stored). This is beyond me.

My suspicion now is otp failure code 2 (which is the original problem
we're discussing) does not necessarily mean that otp failed entirely.
That's why I asked about mac address you were getting with the generic
(the one that can be found in Kalle's github or the one that's in
vanilla OpenWRT) board.bin and firmware-2.bin. Another person reported
[1] they got 00:03:07:12:34:56 mac when with old ath10k (before otp
result was verified) but your uart dump suggests you got a non-generic
mac. I'd like to establish under what circumstances you got your mac.

To recapitulate, can you please check what mac address your wlan interface has:

 a) with otp failure ignored, try board.bin and 10.1.467
firmware-2.bin both as found in vanilla OpenWRT (or from Kalle's
github)
 b) with otp failure ignored, try board.bin as extracted from the
calibration mtd partition but firmware-2.bin as found in vanilla
OpenWRT
 c) with otp failure ignored, try board.bin as extracted from the
calibration mtd partition but firmware-2.bin that I provided in the
OpenWRT ticket[2]

[1]: https://dev.openwrt.org/ticket/16589#comment:4
[2]: https://dev.openwrt.org/ticket/16589


Michał