[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 12 Dec 2016 09:32:26 +0100
From: Rafał Miłecki <zajec5@...il.com>
To: Johannes Berg <johannes@...solutions.net>
Cc: Ming Lei <ming.lei@...onical.com>,
"Luis R. Rodriguez" <mcgrof@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"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 12 December 2016 at 09:12, Johannes Berg <johannes@...solutions.net> wrote:
> On Sat, 2016-12-10 at 16:54 +0100, Rafał Miłecki wrote:
>> 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).
Good to know it may help others as well!
> 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?
OK! If noone will come with any special comments/ideas soon, I'll
propose a patch for using some flags.
FWIW, meanwhile I submitted
[PATCH V2] firmware: simplify defining and handling FW_OPT_FALLBACK
https://patchwork.kernel.org/patch/9469875/
--
Rafał
Powered by blists - more mailing lists