Return-path: Received: from mail-ee0-f46.google.com ([74.125.83.46]:41956 "EHLO mail-ee0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758370Ab2CSXCN (ORCPT ); Mon, 19 Mar 2012 19:02:13 -0400 Received: by eekc41 with SMTP id c41so2875600eek.19 for ; Mon, 19 Mar 2012 16:02:12 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20120130184446.GB2493@tuxdriver.com> <20120315110219.GA2335@redhat.com> <20120317143640.GC23594@khazad-dum.debian.net> From: Julian Calaby Date: Tue, 20 Mar 2012 10:01:51 +1100 Message-ID: (sfid-20120320_000216_963010_250BBEEA) Subject: Re: MAINTAINER NEEDED -- Re: status of ipw2x00 To: Stanislav Yakovlev Cc: Henrique de Moraes Holschuh , Stanislaw Gruszka , "John W. Linville" , Tom Gundersen , Wey-Yi Guy , linux-wireless@vger.kernel.org, Kay Sievers Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi Stanislav, On Tue, Mar 20, 2012 at 09:56, Stanislav Yakovlev wrote: > Hello Henrique, > > On 17 March 2012 07:36, Henrique de Moraes Holschuh wrote: >> 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. >From what I understand, this usually happens when something goes horribly wrong and the only solution is to re-start the card from scratch. Reloading a module to do that isn't such a bad thing, but it would arguably be better if it happened automatically. I believe that this is one of the reset options for modern Intel cards. Thanks, -- Julian Calaby Email: julian.calaby@gmail.com Profile: http://www.google.com/profiles/julian.calaby/ .Plan: http://sites.google.com/site/juliancalaby/