From: Johannes Berg <johannes@sipsolutions.net>
To: "Rafał Miłecki" <zajec5@gmail.com>,
"Ming Lei" <ming.lei@canonical.com>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
brcm80211 development <brcm80211-dev-list@broadcom.com>
Subject: Re: Could we have request_firmware_nowait with FW_OPT_NO_WARN?
Date: Mon, 12 Dec 2016 09:12:19 +0100 [thread overview]
Message-ID: <1481530339.4067.1.camel@sipsolutions.net> (raw)
In-Reply-To: <CACna6rxOGo0e9U7eXpUgnnBuxL+x1B0JBf9ZBq2WPbaBE=YZ-g@mail.gmail.com> (sfid-20161210_165513_587245_23610C6B)
On Sat, 2016-12-10 at 16:54 +0100, Rafał Miłecki wrote:
> Hi,
>
> In brcmfmac we use request_firmware_nowait and if fetching firmware
> with NVRAM variables fails then we try to fallback to the platform
> one (see brcmf_fw_request_code_done & brcmf_fw_request_nvram_done).
>
> Some problem for us is that on devices with platform NVRAM we get
> this error:
> Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2
This also happens with iwlwifi, because it requests multiple firmware
versions starting at the most recent supported one (which is often not
released at the same time).
So yeah, this would be really useful - why don't you just make a patch
with some kind of flags, whether it's FW_OPT_* or new flags?
johannes
next prev parent reply other threads:[~2016-12-12 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 15:54 Could we have request_firmware_nowait with FW_OPT_NO_WARN? Rafał Miłecki
2016-12-12 8:12 ` Johannes Berg [this message]
2016-12-12 8:32 ` Rafał Miłecki
2016-12-12 9:26 ` Arend Van Spriel
2016-12-12 9:53 ` Rafał Miłecki
2016-12-12 14:07 ` Luis R. Rodriguez
2016-12-12 14:16 ` Rafał Miłecki
2016-12-12 11:48 ` Kalle Valo
2016-12-12 14:13 ` Luis R. Rodriguez
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=1481530339.4067.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=brcm80211-dev-list@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=ming.lei@canonical.com \
--cc=zajec5@gmail.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