All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"j@w1.fi" <j@w1.fi>, Kalle Valo <kalle.valo@nokia.com>
Subject: Re: [PATCH v3 1/1] mac80211: tell driver when dtim change detected
Date: Mon, 25 Jan 2010 10:18:57 -0800	[thread overview]
Message-ID: <43e72e891001251018h1a62e1ccn4a7d1411fa2c0615@mail.gmail.com> (raw)
In-Reply-To: <1264250814.2593.25.camel@johannes.local>

On Sat, Jan 23, 2010 at 4:46 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Fri, 2010-01-22 at 16:22 -0800, Guy, Wey-Yi wrote:
>
>> > > We are doing Power consumption test with different DTIM value, the test
>> > > is based on test scripts, so we disable the NetworkManager to make sure
>> > > we can control which AP we need to associated with. During the test, we
>> > > notice when AP change it DTIM value, a lot time STA will used the old
>> > > DTIM value in Power Save mode which cause problem.
>> >
>> > Ah I see. What if there was no old dtim value before?
>>
>> I am not sure, I believe the default is "1", but I might be wrong
>
> Yes, since 0 is nonsensical, we would use 1 instead.

OK -- it seems we have a consensus waiting for a beacon would be good,
but it would be good to have something in for stable. Is the patch Guy
posted acceptable for that purpose? That is, merge this for now until
we get beacon wait implemented prior to association.

  Luis

  reply	other threads:[~2010-01-25 18:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21 21:39 [PATCH v3 1/1] mac80211: tell driver when dtim change detected wey-yi.w.guy
2010-01-22 19:03 ` Johannes Berg
2010-01-22 19:20   ` Luis R. Rodriguez
2010-01-22 19:46     ` Johannes Berg
2010-01-22 23:44       ` Luis R. Rodriguez
2010-01-22 23:45         ` Luis R. Rodriguez
2010-01-23  0:11         ` Guy, Wey-Yi
2010-01-23  0:23           ` Luis R. Rodriguez
2010-01-23  0:22             ` Guy, Wey-Yi
2010-01-23 12:46               ` Johannes Berg
2010-01-25 18:18                 ` Luis R. Rodriguez [this message]
2010-01-25 18:33                   ` Johannes Berg
2010-01-25 19:55                     ` Luis R. Rodriguez
2010-01-25 20:06                       ` Johannes Berg
2010-01-26  8:41                         ` Kalle Valo
2010-01-25 18:32         ` Jouni Malinen
2010-01-25 18:36           ` Johannes Berg
2010-01-25 18:38             ` Johannes Berg
2010-01-23  8:23   ` Kalle Valo
2010-01-25 18:35   ` Jouni Malinen
2010-01-25 20:11     ` Johannes Berg
2010-01-25 20:46       ` Guy, Wey-Yi

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=43e72e891001251018h1a62e1ccn4a7d1411fa2c0615@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=kalle.valo@nokia.com \
    --cc=linux-wireless@vger.kernel.org \
    --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.