From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Wilco Baan Hofman <wilco@baanhofman.nl>
Cc: ath10k@lists.infradead.org
Subject: Re: num_rf_chains problem
Date: Wed, 24 Dec 2014 16:46:44 +0200 [thread overview]
Message-ID: <87a92d9kbv.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <549AD03D.4070607@baanhofman.nl> (Wilco Baan Hofman's message of "Wed, 24 Dec 2014 15:39:57 +0100")
Wilco Baan Hofman <wilco@baanhofman.nl> writes:
> On 23/12/14 08:52, Kalle Valo wrote:
>> Wilco Baan Hofman <wilco@baanhofman.nl> writes:
>>
>>> I'm currently setting up openwrt with the latest git ath10k on the
>>> Engenius ESR1750.
>>>
>>> A couple of things are off:
>>> - My chip shipped with regdomain code 0x00
>>> - OTP calibration is missing?
>>> - DFS pattern detector is not working, possibly because of OTP missing
>>> - num_rf_chains is reported as 2, which is wrong, it should be 3.
>> Most likely the calibration data is somewhere in the host flash (a small
>> MTD partion), there are already products which do that. The size of the
>> calibration data should be 2116 bytes.
>>
>> That would explain why the OTP in the chip itself is empty.
>
> Thanks! I have found a caldata MTD partition, but it contains quite a
> bit of data.. is there a signature I can check for the start (or end) of
> the calibration data?
The MAC address is something to search for and the board.bin file has
similar data format:
https://github.com/kvalo/ath10k-firmware/blob/master/ath10k/QCA988X/hw2.0/board.bin
Most likely the data starts from an even offset like 0x5000 or similar.
This was discussed before on this list, the archives might have more
hints.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-12-24 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 19:48 num_rf_chains problem Wilco Baan Hofman
2014-12-23 7:52 ` Kalle Valo
2014-12-24 14:39 ` Wilco Baan Hofman
2014-12-24 14:46 ` Kalle Valo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a92d9kbv.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=wilco@baanhofman.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox