From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>,
Jouni Malinen <j@w1.fi>,
linux-wireless <linux-wireless@vger.kernel.org>,
Stephen Chen <Stephen.Chen@atheros.com>
Subject: Re: Generic events for wake up from S1-S4
Date: Wed, 15 Jul 2009 08:56:08 -0700 [thread overview]
Message-ID: <43e72e890907150856x50735aafv8e3209f16ded7e37@mail.gmail.com> (raw)
In-Reply-To: <43e72e890907150851m69cd2de6lfb71596fbfac30e6@mail.gmail.com>
On Wed, Jul 15, 2009 at 8:51 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> On Tue, Jul 14, 2009 at 4:53 PM, Pavel Machek<pavel@ucw.cz> wrote:
>> I thought that wifi stack is in software -> you need
>> main cpu to run for wifi to work?
>
> Yes, but we are not processing 802.11 frames for data processing and
> sending them up to any higher layer, we're just doing raw hardware
> pattern matching and event triggering. This of course also means
> devices which do not a CPU or a CPU but no special WoW firmware that
> you won't be able to use WPA for group key stuff for example for which
> I do believe we do need the box's CPU. Which reminds me, maybe we
> should not allow WoW for that case for now.
I should clarify a little more here. It is true you need the main CPU
for wifi to "work", but you don't need it to have the wireless
device's radio turned on, or other logical components of the hardware
sending a PCI PME, for example. All you need for that is some juice.
"Work" in the usual sense would mean to process your raw 802.11
frames, and send them up the stack. That's the part we leave off to
the CPU/driver.
Luis
next prev parent reply other threads:[~2009-07-15 15:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 22:11 Luis R. Rodriguez
2009-07-14 23:53 ` Pavel Machek
2009-07-15 15:51 ` Luis R. Rodriguez
2009-07-15 15:56 ` Luis R. Rodriguez [this message]
2009-07-15 18:00 ` Luis R. Rodriguez
2009-07-18 10:37 ` Pavel Machek
2009-07-18 20:02 ` Luis R. Rodriguez
2009-07-18 23:56 ` Henrique de Moraes Holschuh
2009-07-20 16:27 ` Luis R. Rodriguez
2009-07-21 15:10 ` Henrique de Moraes Holschuh
2009-07-23 14:57 ` Pavel Machek
2009-07-23 18:57 ` Henrique de Moraes Holschuh
2009-07-23 19:13 ` Pavel Machek
2009-07-23 19:45 ` Henrique de Moraes Holschuh
2009-07-23 19:51 ` Pavel Machek
2009-07-23 20:10 ` Henrique de Moraes Holschuh
2009-07-23 21:27 ` Rafael J. Wysocki
2009-07-24 0:53 ` ykzhao
2009-07-24 13:39 ` Henrique de Moraes Holschuh
2009-07-24 14:49 ` Johannes Berg
2009-07-24 15:25 ` Luis R. Rodriguez
2009-07-23 20:31 ` Valdis.Kletnieks
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=43e72e890907150856x50735aafv8e3209f16ded7e37@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=Stephen.Chen@atheros.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®