Return-path: Received: from out1-smtp.messagingengine.com ([66.111.4.25]:35131 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751254Ab2CQOgq (ORCPT ); Sat, 17 Mar 2012 10:36:46 -0400 Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id E5CF320E45 for ; Sat, 17 Mar 2012 10:36:45 -0400 (EDT) Date: Sat, 17 Mar 2012 11:36:41 -0300 From: Henrique de Moraes Holschuh To: Stanislav Yakovlev Cc: Stanislaw Gruszka , "John W. Linville" , Tom Gundersen , Wey-Yi Guy , linux-wireless@vger.kernel.org, Kay Sievers Subject: Re: MAINTAINER NEEDED -- Re: status of ipw2x00 Message-ID: <20120317143640.GC23594@khazad-dum.debian.net> (sfid-20120317_153652_389289_80B12047) References: <20120130184446.GB2493@tuxdriver.com> <20120315110219.GA2335@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, 15 Mar 2012, Stanislav Yakovlev wrote: > On 15 March 2012 04:02, Stanislaw Gruszka 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... -- "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