From: Kalle Valo <Kalle.Valo@nokia.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jouni Malinen <j@w1.fi>, Michael Buesch <mb@bu3sch.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
Ben Greear <greearb@candelatech.com>,
Michael Wu <flamingice@sourmilk.net>, Jiri Benc <jbenc@suse.cz>
Subject: Re: [RFC] b43: multiple MAC addresses support
Date: Thu, 15 Nov 2007 11:35:29 +0200 [thread overview]
Message-ID: <877ikjsvfi.fsf@nokia.com> (raw)
In-Reply-To: <1194953217.9116.38.camel@johannes.berg> (ext Johannes Berg's message of "Tue\, 13 Nov 2007 12\:26\:57 +0100")
Johannes Berg <johannes@sipsolutions.net> writes:
> On Mon, 2007-11-12 at 13:14 +0200, Kalle Valo wrote:
>
>> Exactly, it is important for small mobile devices that beacons are
>> sent at the correct time. For example, I have seen broken APs which
>> Target Beacon Transmission Time fluctuates and Nokia N800 has high
>> power consumption because of that.
>
> The N800 and similar devices only wake up at DTIM beacons, right?
At least N800 and N810 do, we don't want to miss any of broadcast and
multicast traffic. But I don't know how other mobile devices wakeup
for beacons.
> So another idea would be to burst beacons but make sure the DTIM
> beacon time doesn't fluctuate away from the DTIM TBTT. This would be
> possible by changing the order of the beacons and adjusting the DTIM
> count so that the beacon with DTIM count zero is always the first.
At least from my point of view that could possible. Of course it feels
like a bit of a hack, but I guess there's no clean way to implement
this.
--
Kalle Valo
next prev parent reply other threads:[~2007-11-15 9:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 1:43 [RFC] b43: multiple MAC addresses support Johannes Berg
2007-11-09 10:33 ` Johannes Berg
2007-11-09 10:52 ` Johannes Berg
2007-11-11 2:58 ` Jouni Malinen
2007-11-12 11:14 ` Kalle Valo
2007-11-13 11:26 ` Johannes Berg
2007-11-15 9:35 ` Kalle Valo [this message]
2007-11-15 16:40 ` Johannes Berg
2007-11-18 23:02 ` Jouni Malinen
2007-11-19 14:50 ` Johannes Berg
2007-11-13 14:14 ` Johannes Berg
2007-11-12 12:02 ` Johannes Berg
2007-11-18 23:47 ` Jouni Malinen
2007-11-19 14:49 ` Johannes Berg
2007-11-09 10:53 ` [RFC] b43: fix multi MAC address hardware crypto support Johannes Berg
2007-11-09 12:39 ` Johannes Berg
2007-11-10 1:21 ` [RFC v2] " Johannes Berg
2007-11-09 12:25 ` [RFC] b43: multiple MAC addresses support Johannes Berg
2007-11-10 1:20 ` [RFC v2] " Johannes Berg
2007-11-10 1:53 ` [RFC] " Johannes Berg
2007-11-10 21:34 ` Johannes Berg
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=877ikjsvfi.fsf@nokia.com \
--to=kalle.valo@nokia.com \
--cc=flamingice@sourmilk.net \
--cc=greearb@candelatech.com \
--cc=j@w1.fi \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).