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: Thu, 09 Mar 2017 11:59:08 +0100 [thread overview]
Message-ID: <6104737.JakpnjT6P9@bentobox> (raw)
In-Reply-To: <CAJ-Vmom6_-PAnwSjuA5t3a1AKrLhi58ufkLYAjJZkkD5nneusQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1355 bytes --]
On Dienstag, 7. März 2017 08:30:54 CET Adrian Chadd wrote:
> "use your own bmi ids". :-)
>
> (yeah, this is going to make open source firmware for these things
> more painful than it should be. :( )
Thanks for the reply. I was just informed that the firmware binary will behave
differently depending on the bmi-board-id (even when the rest of the content
is the same).
The selection of an own bmi id is therefore also not an actual option. Ok,
maybe in some cases but not in general.
The method to have a single board-2.bin for QCA4019 and to let ath10k select
the right one using bmi-board-id, bmi-chip-id and bus is simply not working.
Either the board-2.bin is simply not used and only the pre-cal data is used
(as seen in Christian Lamparter's/Michal Kazior's patch [1]) or each board has
to come with its own board-2.bin. The latter brings up the license problem
mentioned by Christian [2]. Both have the problem that QCA (for some reason)
wants that always the board-2.bin is used which comes with the "ath10k"
firmware binary [3].
Kind regards,
Sven
[1] https://www.mail-archive.com/ath10k@lists.infradead.org/msg05911.html
[2] https://www.mail-archive.com/ath10k@lists.infradead.org/msg06509.html
[3] btw. this QCA seems to contradict itself here by helping ODMs to
create their own boardata files
[-- 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-09 10:59 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 [this message]
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=6104737.JakpnjT6P9@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.