All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: linux-wireless@vger.kernel.org
Subject: Re: iwl3945 and power saving
Date: Wed, 17 Mar 2010 15:34:20 -0400	[thread overview]
Message-ID: <jwvr5niiw6r.fsf-monnier+gmane.linux.kernel.wireless.general@gnu.org> (raw)
In-Reply-To: 1268804105.2446.620.camel@rchatre-DESK

>> The extra power consumption is quite significant, so I'm considering
>> compiling my own driver, manually re-enabling the power-saving code.
> You will need to revert "iwl3945: disable power save" and then also
> enable power savings using "iwconfig wlanX power on"

Yes, thank you.

>> But before I do that, I'd like to know what is the risk involved (it
>> seems pretty serious since it warranted removing the feature
>> altogether, even tho it was runtime-disabled by default anyway).
> You should find all the details in
> http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2125

Hmm... it seems odd to completely kill the feature rather than to flag
it as "beware, it's brittle" (e.g. only allow to turn it on with
"iwconfig wlanX power on-and-I-promise-I-wont-report-a-bug-if-its-buggy").

Also, it puzzles me: my 3945 has been working fine with power-saving for
more than 2 years (and earlier with ipw3945 as well) and I haven't
noticed any unreliability.  Have I just been lucky or did the problem
only start to manifest in more "recent" versions of the driver, for
reasons we don't understand?


        Stefan


  reply	other threads:[~2010-03-17 19:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17  4:49 iwl3945 and power saving Stefan Monnier
2010-03-17  5:35 ` reinette chatre
2010-03-17 19:34   ` Stefan Monnier [this message]
2010-03-19 16:48     ` reinette chatre
2010-03-19 21:41       ` Stefan Monnier
2010-03-19 22:09         ` reinette chatre
2010-03-20 18:52           ` Stefan Monnier

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=jwvr5niiw6r.fsf-monnier+gmane.linux.kernel.wireless.general@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=linux-wireless@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.