From: Marcel Holtmann <marcel@holtmann.org>
To: Kai Heng Feng <kai.heng.feng@canonical.com>
Cc: Matt Chen <mattsled@gmail.com>,
Luciano Coelho <luciano.coelho@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Johannes Berg <johannes.berg@intel.com>,
"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
linuxwifi@intel.com, Kalle Valo <kvalo@codeaurora.org>,
"David S. Miller" <davem@davemloft.net>,
linux-wireless <linux-wireless@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH 3/3] iwlwifi: Load firmware exclusively for Intel WiFi
Date: Wed, 3 Oct 2018 20:25:18 +0200 [thread overview]
Message-ID: <910F8A29-3141-422F-87EE-7BFBCDE9060C@holtmann.org> (raw)
In-Reply-To: <24BAAAAB-17E4-4820-A09A-50984B8EBA40@canonical.com>
Hi Kai-Heng,
>> I think Canonical were facing some wifi fw load error from some 8260
>> earlier module during the BT still loading the fw.
>> I believe we had later 8260 sku that fixed this issue.
>
> But there are already 8260 that is affected by this bug in the wild.
>
> Search "Bluetooth: hci0: Failed to send firmware data (-38)” and there are lots of user are affected.
which SKUs are these actually. What are the initial details about the boot loader. For the Bluetooth side, you should be able to grab them from dmesg or by running btmon.
So I am not in favor of this kind of hack and creating dependencies between drivers. If you only have a hammer, then everything looks like a nail. And this is a massive hammer trying to squash everything. This problem needs to be debugged. And this starts by providing affected SKU information and firmware information. So get the details about the SKU and its Bluetooth and WiFi boot loaders.
Regards
Marcel
next prev parent reply other threads:[~2018-10-03 18:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 7:15 [PATCH 3/3] iwlwifi: Load firmware exclusively for Intel WiFi Kai-Heng Feng
2018-10-03 7:24 ` Luciano Coelho
2018-10-03 7:27 ` Kai Heng Feng
2018-10-03 7:29 ` Matt Chen
2018-10-03 7:38 ` Kai Heng Feng
2018-10-03 18:25 ` Marcel Holtmann [this message]
2018-10-05 8:30 ` Kai Heng Feng
2018-11-09 0:08 ` João Paulo Rechi Vita
2018-11-09 0:11 ` João Paulo Rechi Vita
2018-11-09 7:49 ` Marcel Holtmann
[not found] ` <CA+A7VXXfdyLWMpNaEzUzDe6PiktOKb5oJrufYrGeTyXyXChQfw@mail.gmail.com>
2018-12-05 19:27 ` João Paulo Rechi Vita
2019-01-09 0:26 ` João Paulo Rechi Vita
2019-01-09 18:39 ` Emmanuel Grumbach
2019-01-10 1:29 ` João Paulo Rechi Vita
2018-10-03 8:58 ` Kalle Valo
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=910F8A29-3141-422F-87EE-7BFBCDE9060C@holtmann.org \
--to=marcel@holtmann.org \
--cc=davem@davemloft.net \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=kai.heng.feng@canonical.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luciano.coelho@intel.com \
--cc=mattsled@gmail.com \
--cc=netdev@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).