From: reinette chatre <reinette.chatre@intel.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwl3945 and power saving
Date: Fri, 19 Mar 2010 09:48:16 -0700 [thread overview]
Message-ID: <1269017296.2446.1777.camel@rchatre-DESK> (raw)
In-Reply-To: <jwvr5niiw6r.fsf-monnier+gmane.linux.kernel.wireless.general@gnu.org>
On Wed, 2010-03-17 at 12:34 -0700, Stefan Monnier wrote:
> 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").
I do not see a way to communicate this to users.
>
> 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?
The previous power saving implementation was very simple. Nothing was
directed from upper layers and user had to manually choose a power
index, which is communicated to device once and device remained in that
power saving state from then on. Recent advances in power saving meant
that more was asked from devices as they were asked to enter and exit
power saving frequently. This new behavior is what is causing issues in
3945 and 4965.
Reinette
next prev parent reply other threads:[~2010-03-19 16:48 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
2010-03-19 16:48 ` reinette chatre [this message]
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=1269017296.2446.1777.camel@rchatre-DESK \
--to=reinette.chatre@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=monnier@iro.umontreal.ca \
/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