> Am Samstag, 31. Dezember 2011, 19:39:18 schrieb Marek Vasut: > > maybe we should implement such thing into the firmware loader itself? > > Allow it -- for example via some node in /dev -- to force loading > > firmware into some buffer in kernel just before suspend so it'll > > certainly be readily available at resume time? > > This is difficult. We don't know at suspend time which firmware we will > need at resume time. That's not actually true ... you can ask the drivers if they need to load firmware after resume ... that can be implemented and udev can handle it. The driver should know if the hardware it's controlling is stupid or not. > We could keep a record of firmware we needed > to get to the state we are, but this is a very complex scheme. Not really. You might have a device where you load firmware, issue suspend command and then issue resume command, while the device will still retain firmware in it, it'll be only in low power mode throughout the sleep cycle. Then you can have a device that will just power down completely, wiping the firmware from it's memory. And that's what should be taken care of by injecting the firmware before suspend. The driver should be able to tell you if the device is broken and needs this special treatment. This will though delay the time to suspect slightly, but that can be considered a price you have to pay if your hardware is stupid. M > > Regards > Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
