On Fri, Jan 14, 2011 at 8:30 AM, Ben Hutchings [off-list ref] wrote:
This is something I started to implement, but never got finished. I
don't think it can be done without an API change, though, as we need
to know when to drop firmware from the cache. But perhaps this could
be done with a hook in the device-driver binding code.
Or just associate the firmware with a module?
So if the firmware gets loaded, it stays in memory until the module is unloaded?
And this all would only be the case if CONFIG_PM is set, so you'd not
waste memory unnecessarily.
Linus