From: Archisman Maitra <archisman001@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 4/4] ath10k: Enable support for QCA9984
Date: Mon, 9 May 2016 09:46:40 +0000 (UTC) [thread overview]
Message-ID: <loom.20160509T113952-8@post.gmane.org> (raw)
In-Reply-To: 1461164356-9158-5-git-send-email-vthiagar@qti.qualcomm.com
The firmware crashes on applying this patch.. On examining the kernel OOPs,
I have found out that that ath10k_bmi_execute in
drivers/net/wireless/ath/ath10k/core.c when called goes in a loop until
timeout occurs after which it eventually crashes. This is called from
ath10k_core_get_board_id_from_otp in
drivers/net/wireless/ath/ath10k/core.c . As per my understanding, the
binaries of QCA99X0 that I have used for QCA9984 is not the correct one.
Could you clarify?
next prev parent reply other threads:[~2016-05-09 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 14:59 [PATCH 0/4] Add support for QCA9984 Vasanthakumar Thiagarajan
2016-04-20 14:59 ` [PATCH 1/4] ath10k: Move rx_location_info out of struct rx_pkt_end Vasanthakumar Thiagarajan
2016-05-24 17:46 ` [1/4] " Kalle Valo
2016-04-20 14:59 ` [PATCH 2/4] ath10k: Clean up growing hw checks during safe and full reset Vasanthakumar Thiagarajan
2016-04-20 14:59 ` [PATCH 3/4] ath10k: Define rx_ppdu_end for QCA9984 Vasanthakumar Thiagarajan
2016-04-20 14:59 ` [PATCH 4/4] ath10k: Enable support " Vasanthakumar Thiagarajan
2016-05-09 9:46 ` Archisman Maitra [this message]
2016-05-09 10:28 ` Thiagarajan, Vasanthakumar
2016-05-09 10:39 ` Archisman Maitra
2016-05-10 17:46 ` Valo, Kalle
[not found] ` <CAHyQSvLpqRNmTL4Tvb7SDtKptzwejfbB7DeQC3NNMb=qqn06GA@mail.gmail.com>
2016-05-11 7:13 ` Thiagarajan, Vasanthakumar
[not found] ` <CAH1sOKUgb0pGmzN4pAy5GHseAW4QHHgyqJx4kgze5_27R8SKxg@mail.gmail.com>
2016-08-05 10:06 ` Thiagarajan, Vasanthakumar
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=loom.20160509T113952-8@post.gmane.org \
--to=archisman001@gmail.com \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).