All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@open-mesh.com>
To: ath10k@lists.infradead.org
Cc: Christian Lamparter <chunkeey@googlemail.com>,
	Michal Kazior <michal.kazior@tieto.com>
Subject: Re: QCA4019: calibration files and board files
Date: Mon, 23 Jan 2017 09:30:29 +0100	[thread overview]
Message-ID: <1619669.9tDARU0uNP@bentobox> (raw)
In-Reply-To: <1591748.RGYhBEn8I1@bentobox>


[-- Attachment #1.1: Type: text/plain, Size: 1315 bytes --]

On Dienstag, 17. Januar 2017 12:54:52 CET Sven Eckelmann wrote:
> Hi,
> 
> I've just	tested LEDE-IPQ40XX [1] after the official open QSDK 1.1.3 [2] was
> not able to boot on an ap.dk01.1-c1-like device. This seemed to work
> exceptionally well (the device basically worked after the first build) but I
> got a little suspicious when looking at the code which it uses for getting the
> wifi devices up and running.
> 
> Spoiler: My actual questions are at the end of the mail.
[...]
> Questions
> =========
> 
> Which therefore brings me back to the initial questions:
> 
>  * Is it known what was modified in the board data and why the board-2.bin
>    from ath10k/QSDK open don't "work"? At least there must be something
>    essential when each vendor ships completely different versions (according
>    to the LEDE-IPQ40xx package [3]).
>  * How were the board-2.bin files from Christian generated
>    (not the tool to generate the TLV sections of board-2.bin. But the input
>     files used for the actual board data sections).
>  * Is the QCA4019 ath10k board data + cal loading order really correct:
>    - load ART data as pre-cal-* to device
>    - execute BMI_PARAM_GET_EEPROM_BOARD_ID
>    - load correct board data from board-2.bin to device
>    - execute bmi_otp_exe_param

*bump*

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

  reply	other threads:[~2017-01-23  8:31 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 [this message]
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
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=1619669.9tDARU0uNP@bentobox \
    --to=sven.eckelmann@open-mesh.com \
    --cc=ath10k@lists.infradead.org \
    --cc=chunkeey@googlemail.com \
    --cc=michal.kazior@tieto.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.