From: Stanislav Yakovlev <stas.yakovlev@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>,
"John W. Linville" <linville@tuxdriver.com>,
Tom Gundersen <teg@jklm.no>, Wey-Yi Guy <wey-yi.w.guy@intel.com>,
linux-wireless@vger.kernel.org,
Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: MAINTAINER NEEDED -- Re: status of ipw2x00
Date: Mon, 19 Mar 2012 15:56:43 -0700 [thread overview]
Message-ID: <CA++WF2PCO8ZdhfSMs6_gy2gz5OvTkVrGYXm0X6Aicoe5JmK+pg@mail.gmail.com> (raw)
In-Reply-To: <20120317143640.GC23594@khazad-dum.debian.net>
Hello Henrique,
On 17 March 2012 07:36, Henrique de Moraes Holschuh <hmh@hmh.eng.br> wrote:
> On Thu, 15 Mar 2012, Stanislav Yakovlev wrote:
>> On 15 March 2012 04:02, Stanislaw Gruszka <sgruszka@redhat.com> 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.
Stanislav.
> --
> "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
next prev parent reply other threads:[~2012-03-19 22:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 13:42 status of ipw2x00 Tom Gundersen
2012-01-30 14:55 ` Johannes Berg
2012-01-30 15:08 ` Tom Gundersen
2012-01-30 15:28 ` wwguy
2012-01-30 18:44 ` MAINTAINER NEEDED -- " John W. Linville
2012-01-30 19:55 ` Dan Williams
2012-01-30 20:13 ` Florian Fainelli
2012-01-30 20:23 ` Dan Williams
2012-01-30 21:47 ` Julian Calaby
2012-01-30 21:52 ` Florian Fainelli
2012-01-30 21:59 ` Julian Calaby
2012-02-02 10:42 ` Francois Romieu
2012-02-03 20:58 ` Stanislav Yakovlev
2012-02-07 21:27 ` yao zhao
2012-03-15 11:02 ` Stanislaw Gruszka
2012-03-16 4:02 ` Stanislav Yakovlev
2012-03-17 14:36 ` Henrique de Moraes Holschuh
2012-03-19 22:56 ` Stanislav Yakovlev [this message]
2012-03-19 23:01 ` Julian Calaby
2012-03-20 2:11 ` Henrique de Moraes Holschuh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA++WF2PCO8ZdhfSMs6_gy2gz5OvTkVrGYXm0X6Aicoe5JmK+pg@mail.gmail.com \
--to=stas.yakovlev@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=kay.sievers@vrfy.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sgruszka@redhat.com \
--cc=teg@jklm.no \
--cc=wey-yi.w.guy@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).