From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: ath9k-devel@lists.ath9k.org
Subject: WoW patches - if anyone is up for following up with them
Date: Tue, 21 Jul 2009 18:49:34 -0700 [thread overview]
Message-ID: <43e72e890907211849h373a07dcxc6361c1aeb2f20ff@mail.gmail.com> (raw)
I won't have time to finish testing this series and getting it merged
as I need to focus on another driver, I ran into some last issues
where I was seeing the nullfunc frames only be issued if I send a WOL
packet first, not sure what's up with that. Some other issues are the
ath9k: timeout (100000 us) on reg 0x806c: 0xdeadbeef & 0x01f00000 != 0x00000000
ath9k: RX failed to go idle in 10 ms RXSM=0xdeadbeef
after resume (not sure if this was caused by the WoW patches or what)
and the mac80211 WARN on the workqueue running local->suspended is
already true.
I probably won't get to these for a long long while (until I need WoW
for another driver), so in case someone is interesting in this, please
feel free to take them on and work on them.
You'll need two things:
* wireless-testing patches:
http://www.kernel.org/pub/linux/kernel/people/mcgrof/patches/wow-07-21.patch
This has johannes's netns patches since his nl80211 cmd is going in
first and then the WoW patches. I've stuffed some documentation on the
patch file itself to help anyone wishing to push that further,
including examples on how to get the pattern stuff initially done.
* http://www.kernel.org/pub/linux/kernel/people/mcgrof/patches/iw-add-wow.patch
You'll need this to enable WoW. Keep in mind based on feedback you
*need* to be associated to an AP to enable WoW.
Luis
reply other threads:[~2009-07-22 1:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43e72e890907211849h373a07dcxc6361c1aeb2f20ff@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=ath9k-devel@lists.ath9k.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox