Thread (9 messages) 9 messages, 5 authors, 2017-08-10

Re: [PATCH 2/6] wl1251: Use request_firmware_prefer_user() for loading NVS calibration data

From: Arend van Spriel <arend.vanspriel@broadcom.com>
Date: 2017-06-30 21:35:47
Also in: lkml, netdev

Possibly related (same subject, not in this thread)


On 23-06-17 23:53, Luis R. Rodriguez wrote:
On Tue, May 16, 2017 at 10:41:08AM +0200, Arend Van Spriel wrote:
quoted
On 16-5-2017 1:13, Luis R. Rodriguez wrote:
quoted
Since no upstream delta is needed for firmwared I'd like to first encourage
evaluating the above. While distributions don't carry it yet that may be seen as
an issue but since what we are looking for are corner cases, only folks needing
to deploy a specific solution would need it or a custom proprietary solution.
Ok. I will go try and run firmwared in OpenWrt on a router platform.
Have to steal one from a colleague :-p Will study firmwared.
Arend, curious how this effort goes. Its important to me as we know then that
if this works its a good approach to recommend moving forward which should also
prove less complex than that soup we had with the custom fallback stuff.
Hi Luis,

So I looked at firmwared and we basically need to extend it. For our
router platform we need to obtain nvram calibration data from an MTD
partition which contains the raw data, ie. no file-system on it. So
firmwared would need some sort of configuration to map a particular
firmware file to some action obtaining the data like kicking off some
mtd-utils in my case.

Regards,
Arend
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help