On Wednesday 17 May 2017 14:06:06 Johannes Berg wrote:

On Tue, 2017-05-16 at 01:13 +0200, Luis R. Rodriguez wrote:

quoted

quoted

quoted

Now for N900 case there is a similar scenario
alhtough it has additional requirement to go to user-space due to
need to use a proprietary library to obtain the NVS calibration
data. My thought: Why should firmware_class care?

Agreed.

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. Those example calibration data
should not be used for real usage, but Pavel told us that on N900 they
are enough for working WIFI connection. They does not contain valid MAC
address, so kernel should generate some (random?).

So kernel driver should get NVS calibration data from userspace (which
know how where to get or how to prepare them) and in case userspace do
not have it, then we can try fallback to those example data (as people
reported us they can be useful instead of non-working WIFI).

And that fallback is working by direct firmware loading from kernel.

-- 
Pali Rohár
pali.rohar@gmail.com