From: Ryan Hsu <ryanhsu@qti.qualcomm.com>
To: Luka Karinja <luka.karinja@gmail.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: failed to fetch board data QCA6174
Date: Wed, 13 Sep 2017 22:14:55 +0000 [thread overview]
Message-ID: <ef5a7431-deea-05fa-131c-87352201642d@qti.qualcomm.com> (raw)
In-Reply-To: <bb17d89c-3757-1f57-801e-eee70380ad09@gmail.com>
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
next prev parent reply other threads:[~2017-09-13 22:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-11 16:54 Luka Karinja
2017-09-11 21:15 ` Ryan Hsu
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=ef5a7431-deea-05fa-131c-87352201642d@qti.qualcomm.com \
--to=ryanhsu@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=luka.karinja@gmail.com \
/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