From: Andre Valentin <avalentin@marcant.net>
To: Kalle Valo <kvalo@qca.qualcomm.com>,
Helmut Schaa <helmut.schaa@googlemail.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath10k OTP loading issues
Date: Thu, 17 Jul 2014 17:54:54 +0200 [thread overview]
Message-ID: <53C7F1CE.3060501@marcant.net> (raw)
In-Reply-To: <87lhrs6l2r.fsf@kamboji.qca.qualcomm.com>
Hi!
On 17.07.2014 17:50, Kalle Valo wrote:
> Helmut Schaa <helmut.schaa@googlemail.com> writes:
>
>>> But in method 2) otp.bin will fail as there's no data in the OTP area.
>>> This is expected and that's why we should not run otp.bin at all with
>>> method 2).
>>
>> Thanks for clarification Kalle! So, method 2 requires only a
>> board.bin?
>
> Yes. You need to extract the board file from the MTD partition and
> provide it to ath10k.
>
So the question is why does in this case fail the otp.bin loading process or why is it started.
How can I prevent it. I provided the correspondig board.bin. If needed, I could run
a debug on the ath10k loading.
Kind regards,
André
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-07-17 15:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53AD2EEE.4040704@marcant.net>
2014-07-02 8:10 ` ath10k OTP loading issues Kalle Valo
2014-07-07 15:40 ` Helmut Schaa
2014-07-15 21:16 ` Andre Valentin
2014-07-17 14:12 ` Helmut Schaa
2014-07-17 15:03 ` Kalle Valo
2014-07-17 15:45 ` Helmut Schaa
2014-07-17 15:50 ` Kalle Valo
2014-07-17 15:54 ` Andre Valentin [this message]
2014-07-17 15:59 ` Kalle Valo
2014-07-17 21:44 ` Helmut Schaa
2014-07-19 23:46 ` Andre Valentin
2014-07-19 23:57 ` Andre Valentin
[not found] ` <53AD4F17.6070604@marcant.net>
2014-07-02 8:13 ` Kalle Valo
2014-07-02 8:34 ` André Valentin
2014-07-02 8:56 ` Kalle Valo
2014-07-07 14:51 ` André Valentin
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=53C7F1CE.3060501@marcant.net \
--to=avalentin@marcant.net \
--cc=ath10k@lists.infradead.org \
--cc=helmut.schaa@googlemail.com \
--cc=kvalo@qca.qualcomm.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