From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
simon.wunderlich@openmesh.com,
Michal Kazior <michal.kazior@tieto.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: QCA4019: calibration files and board files
Date: Tue, 07 Mar 2017 10:54:19 +0100 [thread overview]
Message-ID: <30387745.tG59X1cezt@bentobox> (raw)
In-Reply-To: <CAJ-Vmom3g+cbNG7hXjUB=Rnh9S_rHmr7hS2Z6H+m=LQCfezBAg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1317 bytes --]
Hi Adrian,
On Montag, 30. Januar 2017 08:36:19 CET Adrian Chadd wrote:
> If people aren't using unique BMI IDs (which is another question we
> have for QCA) then it's possible you don't have enough information to
> "know" which board data to use, so it has to be overridden by a custom
> package. We do this at work for our own boards as well - they're
> sufficiently different to a reference board that indeed we need to
> "know".
Did you get any feedback from QCA? Our requests regarding registration of two
own bmi-board-ids for our product were always answered (slightly simplified)
with "don't change the BDF files", "always use board-2.bin from driver/
firmware" and "ask your ODM". This basically didn't help us and didn't answer
the question and creates quite a big problem for us because the ODM insists
that we should use his BDF [1] files with modifications [tm]. We just found
out that the ODM used a modified version of the DK04.1 BDF files but used the
bmi-board-id's for the AP-DK01.1-C1 - so we still have a long road ahead.
We are still trying to get more information. But I though that I could ask you
in the meantime whether you had more success and have a status update.
Kind regards,
Sven
[1] According to QCA, the BDF files are just the single board files inside
the board-2.bin
[-- 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-07 9:54 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 [this message]
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
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=30387745.tG59X1cezt@bentobox \
--to=sven.eckelmann@openmesh.com \
--cc=adrian@freebsd.org \
--cc=ath10k@lists.infradead.org \
--cc=chunkeey@googlemail.com \
--cc=michal.kazior@tieto.com \
--cc=simon.wunderlich@openmesh.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