From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: Rajkumar Manoharan <rmanohar@codeaurora.org>
Cc: Mohammed Shafi Shajakhan <mohammed@codeaurora.org>,
akolli@codeaurora.org,
Tamizh chelvam <tamizhchelvam@codeaurora.org>,
ath10k@lists.infradead.org, shashidhar.lakkavalli@openmesh.com
Subject: Re: QCA4019: calibration files and board files
Date: Wed, 01 Mar 2017 08:32:57 +0100 [thread overview]
Message-ID: <2041049.sDAvLy9HAv@bentobox> (raw)
In-Reply-To: <821ad665d0934c58fc8b3c830e119433@codeaurora.org>
[-- Attachment #1.1: Type: text/plain, Size: 1289 bytes --]
On Dienstag, 28. Februar 2017 19:22:32 CET Rajkumar Manoharan wrote:
> On 2017-02-27 23:58, Sven Eckelmann wrote:
> > It looks to me now that this information is contradicting your
> > implementation
> > (which now loads the data from 0:ART partition [1] like pre-cal data
> > [2] and
> > then loads the board-2.bin [3]).
> >
> Both reading from ART and loading pre-cal data file are same.
>
> > I have doubt regarding his explanation but I got no actual spec - only
> > information which seems to be contradicting (or to vague) . Is is
> > possible
> > to get some confirmation from you about whether the data from the 0:ART
> > partition is pre-cal data or not and whether the board-2.bin should be
> > used when the data from 0:ART is used.
> >
> In QCA4019 platform, only radio specific calibration (pre-cal-data) is
> stored in flash.
> Board specific contents are read from board-2.bin. For each radio
> appropriate board
> data should be loaded. To fetch correct board data from board-2.bin
> bundle, pre-cal/radio
> specific caldata should be loaded first to get proper board id.
>
> > My understanding until now was that:
> >
> > * pre-cal data + board-2.bin info == actual calibration data
> >
> Correct.
[...]
Thanks a lot for the confirmation
Kind regards,
Sven
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-03-01 7:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 11:54 QCA4019: calibration files and board files Sven Eckelmann
2017-01-23 8:30 ` Sven Eckelmann
2017-01-30 16:36 ` Adrian Chadd
2017-01-31 10:12 ` Sven Eckelmann
2017-03-07 9:54 ` Sven Eckelmann
2017-03-07 16:30 ` Adrian Chadd
2017-03-09 10:59 ` Sven Eckelmann
2017-03-09 11:51 ` Valo, Kalle
2017-03-09 12:46 ` Sven Eckelmann
2017-03-09 12:54 ` Sven Eckelmann
2017-03-09 13:11 ` Christian Lamparter
2017-03-09 14:18 ` Waldemar Rymarkiewicz
2017-03-09 16:11 ` Adrian Chadd
2017-02-08 11:03 ` Sven Eckelmann
2017-02-09 10:26 ` akolli
2017-02-09 10:44 ` Adrian Chadd
2017-02-28 7:58 ` Sven Eckelmann
2017-03-01 3:22 ` Rajkumar Manoharan
2017-03-01 7:32 ` Sven Eckelmann [this message]
2017-03-01 12:51 ` Christian Lamparter
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=2041049.sDAvLy9HAv@bentobox \
--to=sven.eckelmann@openmesh.com \
--cc=akolli@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=mohammed@codeaurora.org \
--cc=rmanohar@codeaurora.org \
--cc=shashidhar.lakkavalli@openmesh.com \
--cc=tamizhchelvam@codeaurora.org \
/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