[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 12 Dec 2016 09:12:19 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Rafał Miłecki <zajec5@...il.com>,
Ming Lei <ming.lei@...onical.com>,
"Luis R. Rodriguez" <mcgrof@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc: "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
brcm80211 development <brcm80211-dev-list@...adcom.com>
Subject: Re: Could we have request_firmware_nowait with FW_OPT_NO_WARN?
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
Powered by blists - more mailing lists