On Mon, 19 Mar 2012, Stanislav Yakovlev wrote: > Hello Henrique, > On 17 March 2012 07:36, Henrique de Moraes Holschuh <hmh@xxxxxxxxxx> wrote: > > On Thu, 15 Mar 2012, Stanislav Yakovlev wrote: > >> On 15 March 2012 04:02, Stanislaw Gruszka <sgruszka@xxxxxxxxxx> wrote: > >> > Are you plan to fix issues caused on current firmware loading changes on > >> > linux? > >> > >> I was able to reproduce this issue; unfortunately, I don't have a > >> proper fix for it yet. > > > > Maybe you could delay the firmware load to when the device is opened (at > > which point you can probably change the driver to keep the device in PCI > > D3 state unless it is opened, which does save power), and just caching > > the firmware forever after the first load so that you don't need to > > request_firmware anything more than once. > > > > Chances are ipw2xxx firmware will never get a new revision anyway, so > > reloading the modules is not too large a price to pay if the user does > > decide he has to force a firmware refresh... > > As far as I know there is no way to force firmware refresh at the > moment without reloading the driver. If you know any implementations > of such behavior, please let me know. You just need to switch modes, which forces it to switch firmwares, and it always reloads it from disk (unless you've built it in the kernel, maybe. I didn't try that). -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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
