From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Dan Williams <dcbw@redhat.com>,
"Guy, Wey-Yi W" <wey-yi.w.guy@intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Kalle Valo <kalle.valo@iki.fi>, Matthew Garrett <mjg@redhat.com>,
Marcel Holtmann <marcel@holtmann.org>, Jouni Malinen <j@w1.fi>
Subject: Re: wireless powersaving (in NM?)
Date: Thu, 26 Mar 2009 09:11:00 +0100 [thread overview]
Message-ID: <1238055060.4331.1.camel@johannes.local> (raw)
In-Reply-To: <43e72e890903260100w75896d0fi9121f227cc7ca8dc@mail.gmail.com> (sfid-20090326_090603_527463_A3630685)
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
On Thu, 2009-03-26 at 01:00 -0700, Luis R. Rodriguez wrote:
> > Right. If a particular chipset doesn't properly supported PS then we
> > shouldn't actually support it at all -- but we cannot know if the AP is
> > broken.
>
> How about leaving it to the supplicant to guess if the AP is borked or not.
>
> Kalle, what would happen with these broken APs?
We talked about that briefly yesterday -- it's not very easy to
determine this because of the various ways things break:
* one AP sets the broadcast/multicast bit one beacon too late (after
having already sent the frames)
* one AP doesn't buffer frames at all
* one AP doesn't respond to PS-poll frames
etc.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-03-26 8:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 10:39 wireless powersaving (in NM?) Johannes Berg
2009-03-24 10:32 ` Marcel Holtmann
2009-03-25 10:45 ` Johannes Berg
2009-03-24 13:47 ` John W. Linville
2009-03-24 13:53 ` Johannes Berg
2009-03-24 14:47 ` Guy, Wey-Yi W
2009-03-24 15:03 ` Kalle Valo
2009-03-24 14:17 ` Kalle Valo
2009-03-25 10:57 ` Johannes Berg
2009-03-25 19:53 ` Kalle Valo
2009-03-25 20:06 ` Johannes Berg
2009-03-25 20:09 ` Johannes Berg
2009-03-25 20:22 ` Kalle Valo
2009-03-24 15:59 ` Dan Williams
2009-03-25 11:04 ` Johannes Berg
2009-03-25 15:31 ` Dan Williams
2009-03-25 15:48 ` Johannes Berg
2009-03-26 8:00 ` Luis R. Rodriguez
2009-03-26 8:11 ` Johannes Berg [this message]
2009-03-26 8:39 ` Luis R. Rodriguez
2009-03-26 8:54 ` Johannes Berg
2009-03-26 9:01 ` Luis R. Rodriguez
2009-03-26 14:29 ` Georgy Berdyshev
2009-03-26 8:19 ` Kalle Valo
2009-03-26 8:40 ` Luis R. Rodriguez
2009-03-31 16:28 ` Johannes Berg
2009-04-01 11:04 ` more thoughts on power saving (was: wireless powersaving (in NM?)) Johannes Berg
2009-04-01 11:12 ` Kalle Valo
2009-04-01 14:29 ` Guy, Wey-Yi W
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=1238055060.4331.1.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--cc=j@w1.fi \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mcgrof@gmail.com \
--cc=mjg@redhat.com \
--cc=wey-yi.w.guy@intel.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 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.