Re: [PATCH 2/6] wl1251: Use request_firmware_prefer_user() for loading NVS calibration data
From: Johannes Berg <johannes@sipsolutions.net>
Date: 2017-05-17 13:05:04
Also in:
linux-wireless, lkml
Possibly related (same subject, not in this thread)
- 2017-08-10 · Re: [PATCH 2/6] wl1251: Use request_firmware_prefer_user() for loading NVS calibration data · "Luis R. Rodriguez" <mcgrof@kernel.org>
- 2017-06-30 · Re: [PATCH 2/6] wl1251: Use request_firmware_prefer_user() for loading NVS calibration data · Arend van Spriel <arend.vanspriel@broadcom.com>
- 2017-06-23 · Re: [PATCH 2/6] wl1251: Use request_firmware_prefer_user() for loading NVS calibration data · "Luis R. Rodriguez" <mcgrof@kernel.org>
- 2017-05-18 · Re: [PATCH 2/6] wl1251: Use request_firmware_prefer_user() for loading NVS calibration data · Bjorn Andersson <hidden>
- 2017-05-17 · Re: [PATCH 2/6] wl1251: Use request_firmware_prefer_user() for loading NVS calibration data · Johannes Berg <johannes@sipsolutions.net>
On Wed, 2017-05-17 at 14:53 +0200, Pali Rohár wrote:
quoted
In fact, why should the *driver* care either? IOW - why should "request_firmware_prefer_user()" even exist?There are default/example NVS data, which are stored in /lib/firmware and installed by linux-firmware package.
[...] Oh, so you're saying you want this to invert the order ... Ok, that makes some sense. I still hope that all other requests will eventually fall back to user loading though, I think that's important to system integration in general. johannes