From: Zhu Yi <yi.zhu@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Michael Buesch <mb@bu3sch.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
Tomas Winkler <tomasw@gmail.com>, bruno randolf <br1@einfach.org>,
"Luis R. Rodriguez" <mcgrof@gmail.com>, Jouni Malinen <j@w1.fi>
Subject: Re: hardware/firmware powersave help, Broadcom scheme
Date: Mon, 25 Feb 2008 14:30:25 +0800 [thread overview]
Message-ID: <1203921025.3090.9.camel@debian.sh.intel.com> (raw)
In-Reply-To: <1203688708.7082.22.camel@johannes.berg>
On Fri, 2008-02-22 at 14:58 +0100, Johannes Berg wrote:
> I thought you just said the firmware follows the powersave transitions
> by itself (by looking at the frames)? In my hypothetical scheme the
> driver/stack notifies the firmware about them.
Alright, the iwlwifi firmware works partially by itself on powersave. It
switches from wake to sleep by looking at the frames and from sleep to
wake by driver/stack notification.
BTW, I've put our iwl4965 AP code at below address. We tested it on
2.6.22 kernel. The code is not very up to date but you can at least get
a working AP with an iwl4965 card.
http://www.kernel.org/pub/linux/kernel/people/chuyee/wireless/iwl4965_ap/
To install mac80211:
$ cd mac80211
$ make patch_kernel
$ recompile your kernel and modules && install
To compile and run the hostapd:
$ cd hostapd
$ make KSRC=/lib/modules/`uname -r`/build
$ ./hostapd hostapd.conf
Thanks,
-yi
prev parent reply other threads:[~2008-02-25 6:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 15:18 hardware/firmware powersave help, Broadcom scheme Johannes Berg
2008-02-21 6:12 ` Zhu Yi
2008-02-21 10:58 ` Johannes Berg
2008-02-21 11:04 ` Johannes Berg
2008-02-22 3:45 ` Zhu Yi
2008-02-22 13:58 ` Johannes Berg
2008-02-25 6:30 ` Zhu Yi [this message]
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=1203921025.3090.9.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=br1@einfach.org \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=mcgrof@gmail.com \
--cc=tomasw@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;
as well as URLs for NNTP newsgroup(s).