From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ryan Hsu <ryanhsu@qti.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Thorsten Leemhuis <linux@leemhuis.info>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath10k-regression in 4.14: Connections aborts with "failed to extract amsdu: -11"
Date: Sun, 29 Oct 2017 07:06:43 +0000 [thread overview]
Message-ID: <87y3nu4em6.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <46f918c5-b07d-e397-2f3d-8136c7c1a8f3@qti.qualcomm.com> (Ryan Hsu's message of "Mon, 2 Oct 2017 23:40:31 +0000")
+ linux-wireless
Ryan Hsu <ryanhsu@qti.qualcomm.com> writes:
>>> ath10k_pci 0000:3a:00.0: Direct firmware load for
>>> ath10k/pre-cal-pci-0000:3a:00.0.bin failed with error -2
>>> ath10k_pci 0000:3a:00.0: Direct firmware load for
>>> ath10k/cal-pci-0000:3a:00.0.bin failed with error -2
>> Do they have anything to do with this? Hardware is
>
> This error message is confusing since QCA6174 is not supporting
> pre-calibration feature, this reminds me that we need to clean this
> up.
These warnings come up again because of this commit:
c0cc00f250e1 ath10k: activate user space firmware loading again
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=ath-next&id=c0cc00f250e19c717fc9cdbdb7f55aaa569c7498
We really need a function like request_firmware_nowarn() which would not
print a warning everytime a file is not found. It just confuses the
users and make them falsely believe that's the reason of their problems.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2017-10-29 7:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 8:59 ath10k-regression in 4.14: Connections aborts with "failed to extract amsdu: -11" Thorsten Leemhuis
2017-10-02 23:40 ` Ryan Hsu
2017-10-08 8:27 ` ath10k-regression due to "ath10k: fix napi_poll budget overflow" c9353bf483d3 (Was: " Thorsten Leemhuis
2017-10-16 9:04 ` ath10k-regression due to "ath10k: fix napi_poll budget overflow" c9353bf483d3 Rouven Czerwinski
2017-10-27 9:40 ` Kalle Valo
2017-10-27 19:01 ` Ryan Hsu
2017-10-29 7:44 ` Kalle Valo
2017-10-29 10:21 ` Thorsten Leemhuis
2017-10-08 9:39 ` Wifi slow on the XPS13 (9360) (QCA6174) (Was Re: ath10k-regression in 4.14: Connections aborts with "failed to extract amsdu: -11") Thorsten Leemhuis
2017-10-29 7:27 ` ath10k: Wifi slow on the XPS13 (9360) (QCA6174) Kalle Valo
2017-10-31 15:47 ` Thorsten Leemhuis
2017-11-01 7:25 ` Kalle Valo
2017-10-29 7:06 ` Kalle Valo [this message]
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=87y3nu4em6.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=ryanhsu@qti.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