From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Tino Keitel <tino.keitel@tikei.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Power saving features for iwl4965
Date: Mon, 7 Jan 2013 12:08:00 +0100 [thread overview]
Message-ID: <20130107110759.GC6931@redhat.com> (raw)
In-Reply-To: <20121226185425.GA12627@x61.home>
Hi
On Wed, Dec 26, 2012 at 07:54:25PM +0100, Tino Keitel wrote:
> On Thu, May 03, 2012 at 20:28:53 +0200, Tino Keitel wrote:
> > On Wed, Apr 25, 2012 at 14:25:55 +0200, Stanislaw Gruszka wrote:
> > > On Wed, Apr 18, 2012 at 10:35:43PM +0200, Tino Keitel wrote:
> > > > up to 2.6.38, the iwl4965 driver was able to use power saving features
> > > > by invoking "iwconfig <interface> power on", at least when unsetting
> > > > the broken_powersave variable.
> > > >
> > > > 2.6.39 introduced a new iwlegacy driver for iwl4965 hardware, which was
> > > > missing power saving. I was able to port the 2.6.38 driver up to
> > > > kernel 3.1, but it got too complicated for me with 3.2.
> > > >
> > > > Are there any plans to fix this power usage regression at some point in
> > > > the iwlegacy driver? I think there are still a lot of iwl4965 users out
> > > > there.
> > > Yes, adding PS support is on my iwlegacy TODO list.
> >
> > Thanks, I'd be glad if I could help, testing etc.
>
> Hi Stanislaw,
>
> is there any progress regarding this? If not, I could try to implement
> it in the current kernel. However, I don't have any knowlegde about
> hardware related features. If you have, maybe I could use your
> knowledge to do it myself.
I posted patch here
http://marc.info/?l=linux-wireless&m=135601033021616&w=2
But I did not review code regarding power save to catch possible
problems. Testing are bug reporting are welcome ...
Thanks
Stanislaw
next prev parent reply other threads:[~2013-01-07 11:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 20:35 Power saving features for iwl4965 Tino Keitel
2012-04-19 14:25 ` Johannes Berg
2012-04-19 18:50 ` tino
2012-04-25 12:25 ` Stanislaw Gruszka
2012-05-03 18:28 ` Tino Keitel
2012-12-26 18:54 ` Tino Keitel
2013-01-07 11:08 ` Stanislaw Gruszka [this message]
2013-01-08 1:48 ` Pedro Francisco
2013-01-08 8:47 ` Stanislaw Gruszka
2013-06-03 8:52 ` Tino Keitel
2013-06-03 14:18 ` Stanislaw Gruszka
2013-06-09 0:28 ` Pedro Francisco
2013-06-10 19:31 ` Pedro Francisco
2013-06-11 16:19 ` Stanislaw Gruszka
2013-06-11 18:55 ` Tino Keitel
2013-06-14 12:50 ` Pedro Francisco
2013-06-14 13:18 ` Stanislaw Gruszka
2013-06-25 14:25 ` Stanislaw Gruszka
2013-07-11 21:02 ` Pedro Francisco
2013-07-16 10:27 ` Stanislaw Gruszka
2013-07-16 11:02 ` Pedro Francisco
2013-07-17 11:48 ` Pedro Francisco
2013-07-31 12:08 ` Stanislaw Gruszka
2013-08-04 14:24 ` Pedro Francisco
2013-08-04 14:53 ` Pedro Francisco
2013-10-17 9:06 ` Stanislaw Gruszka
2013-10-17 13:32 ` Stanislaw Gruszka
2013-06-11 18:51 ` Tino Keitel
2014-02-18 10:57 ` Stanislaw Gruszka
2014-02-18 11:32 ` Emmanuel Grumbach
2014-02-18 11:59 ` Stanislaw Gruszka
2014-02-20 12:08 ` Pedro Francisco
2014-02-25 16:16 ` Pedro Francisco
-- strict thread matches above, loose matches on Subject: below --
2012-10-01 16:06 Tino Keitel
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=20130107110759.GC6931@redhat.com \
--to=sgruszka@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tino.keitel@tikei.de \
/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.