[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1495026290.2442.6.camel@sipsolutions.net>
Date: Wed, 17 May 2017 15:04:50 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Pali Rohár <pali.rohar@...il.com>
Cc: "Luis R. Rodriguez" <mcgrof@...nel.org>,
Arend Van Spriel <arend.vanspriel@...adcom.com>,
Pavel Machek <pavel@....cz>, Daniel Wagner <wagi@...om.org>,
Tom Gundersen <teg@...m.no>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Kalle Valo <kvalo@...eaurora.org>,
David Gnedt <david.gnedt@...izone.at>,
Tony Lindgren <tony@...mide.com>,
Sebastian Reichel <sre@...nel.org>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>,
Aaro Koskinen <aaro.koskinen@....fi>,
Takashi Iwai <tiwai@...e.de>,
AKASHI Takahiro <takahiro.akashi@...aro.org>,
David Woodhouse <dwmw2@...radead.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Grazvydas Ignotas <notasas@...il.com>,
linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
netdev@...r.kernel.org,
Michał Kazior <kazikcz@...il.com>
Subject: Re: [PATCH 2/6] wl1251: Use request_firmware_prefer_user() for
loading NVS calibration data
On Wed, 2017-05-17 at 14:53 +0200, Pali Rohár wrote:
> > 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
Powered by blists - more mailing lists