From: Kalle Valo <kvalo@codeaurora.org>
To: Anil Duggirala <anilduggirala@fastmail.fm>
Cc: debian-kernel@lists.debian.org, ath10k@lists.infradead.org,
Sven Eckelmann <sven.eckelmann@openmesh.com>
Subject: Re: missing firmware in debian 9
Date: Wed, 28 Nov 2018 17:17:15 +0200 [thread overview]
Message-ID: <87d0qp6xl0.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1543415108.3687532.1591824912.00271098@webmail.messagingengine.com> (Anil Duggirala's message of "Wed, 28 Nov 2018 09:25:08 -0500")
Anil Duggirala <anilduggirala@fastmail.fm> writes:
>> > I don't have a QCA6174 hw3.0 but I would guess that ath10k loaded the
>> > firmware-4.bin after it failed to load the firmware-5.bin.
>
> How can I make sure this is the case?
ath10k prints lots of information to dmesg after it has initialised the
device, so check that. You should see the firmware version and what api
is used (the number N from firmware-N.bin).
> I have had a couple of issues with my bluetooth, how can I test it?
The warnings you posted are because ath10k is trying to find optional
calibration data and various firmware versions of firmware file from
user space. The warnings and commit c8e028026387 have nothing to do with
bluetooth, so that must be a separate issue.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-11-28 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 13:38 missing firmware in debian 9 Anil Duggirala
2018-11-26 8:48 ` Sven Eckelmann
2018-11-28 14:03 ` Kalle Valo
2018-11-28 14:17 ` Anil Duggirala
2018-11-28 14:25 ` Anil Duggirala
2018-11-28 15:17 ` Kalle Valo [this message]
2018-11-28 16:47 ` Anil Duggirala
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=87d0qp6xl0.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=anilduggirala@fastmail.fm \
--cc=ath10k@lists.infradead.org \
--cc=debian-kernel@lists.debian.org \
--cc=sven.eckelmann@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