From: Jouni Malinen <jouni.malinen@atheros.com>
To: Davide Pesavento <davidepesa@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
"alexander.bartha@drz-wien.at" <alexander.bartha@drz-wien.at>,
Alexander Bartha <alex.xy.privat@gmx.at>,
linux-wireless <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [ath9k-devel] ath9k module-Unable to set channel-since ath comes
Date: Thu, 14 May 2009 21:44:27 +0300 [thread overview]
Message-ID: <1242326667.14069.20.camel@jm-desktop> (raw)
In-Reply-To: <2da21fe50905120135h1cb8746foae4b3b4b37b3cb24@mail.gmail.com>
On Tue, 2009-05-12 at 01:35 -0700, Davide Pesavento wrote:
> I've already reported ath9k's issues with PS multiple times [1] [2]
> [3], but the driver hasn't been fixed yet. You can find a verbose
> debugging output at [4], I hope that helps in fixing the problem (I
> can provide even more info if needed and I'm willing to test patches).
I submitted a set of patches to resolve some of the PS issues in ath9k.
I would expect these to hit wireless-testing.git eventually, but if you
are willing to test the changes before that, you can find the patches
from http://w1.fi/p/ps/
One thing to note here is that there are still some issues with the
timeout=0 case (use of PS-Poll to fetch buffered frames) which is
enabled with "iwconfig wlan0 power on", so at this point, I would
recommend running the test either with the default wireless-testing.git
PS mode setting or by enabling power saving with "iwconfig wlan0 power
timeout 500ms" which should result in the same configuration.
I have not tested these on AR5418, but at least with AR9280, these
patches do improve stability and general functionality of the default PS
mode considerably. I have been able to run multi-hour tests without
losing connection.
- Jouni
next prev parent reply other threads:[~2009-05-14 18:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090203173228.GB9713@tesla>
[not found] ` <20090206202205.218710@gmx.net>
[not found] ` <20090206211804.GG5031@tesla>
[not found] ` <20090214230618.203560@gmx.net>
[not found] ` <43e72e890902141718v544f5caejb71f53bdadbf8a8f@mail.gmail.com>
[not found] ` <20090216205115.21860@gmx.net>
[not found] ` <43e72e890902161342j23b68a4eoabddb047fb9d9084@mail.gmail.com>
[not found] ` <20090508211237.316290@gmx.net>
[not found] ` <1241818845.6240.4.camel@mj>
[not found] ` <43e72e890905081453h2d660e6dl38b714467c8f24cb@mail.gmail.com>
2009-05-10 18:41 ` [ath9k-devel] ath9k module-Unable to set channel-since ath comes Luis R. Rodriguez
2009-05-11 4:17 ` Pavel Roskin
2009-05-11 7:40 ` Luis R. Rodriguez
2009-05-11 22:06 ` Pavel Roskin
2009-05-11 22:22 ` Luis R. Rodriguez
[not found] ` <OF24E7AF48.E39EC671-ONC12575B4.00236C72-C12575B4.0024C49C@drz-wien.at>
2009-05-12 6:55 ` Luis R. Rodriguez
2009-05-12 7:11 ` Johannes Berg
2009-05-12 7:14 ` Luis R. Rodriguez
2009-05-12 8:35 ` Davide Pesavento
2009-05-14 18:44 ` Jouni Malinen [this message]
2009-05-18 18:10 ` Kalle Valo
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=1242326667.14069.20.camel@jm-desktop \
--to=jouni.malinen@atheros.com \
--cc=alex.xy.privat@gmx.at \
--cc=alexander.bartha@drz-wien.at \
--cc=ath9k-devel@lists.ath9k.org \
--cc=davidepesa@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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