From: bruno randolf <bruno@thinktube.com>
To: Jouni Malinen <j@w1.fi>
Cc: Holger Schurig <hs4233@mail.mn-solutions.de>,
linux-wireless@vger.kernel.org,
cao jing <caojing.china@gmail.com>
Subject: Re: AR5K_INT_SWBA can't generate interruption for sending beacons
Date: Wed, 16 Apr 2008 10:43:01 +0200 [thread overview]
Message-ID: <200804161043.01769.bruno@thinktube.com> (raw)
In-Reply-To: <20080416060109.GG15053@jm.kir.nu>
On Wednesday 16 April 2008 08:01:09 Jouni Malinen wrote:
> On Tue, Apr 15, 2008 at 10:59:05AM +0200, bruno randolf wrote:
> > the current code in wireless-testing uses SWBA not to send beacons but to
> > keep track of the next beacon time NBTT. this is necessary to work around
> > certain hardware limitations. once configured, the beacons are sent
> > automatically by the hardware at the right time. of course it would be
> > possible to change the code to generate a new beacon at every SWBA but as
> > long as the beacon contents don't change very often i don't see the point
> > of doing so.
>
> In AP mode, beacon payload changes for _every beacon_ unless you use
> DTIM Period of 1. In order to make power saving work correctly, the
> drivers need to update the beacon data for every beacon.
thats's true - i was thinking of IBSS mode first of all since AP mode is not
supported yet by ath5k. actually also in IBSS mode the beacon contents would
have to change for power saving, this is also not implemented yet.
bruno
prev parent reply other threads:[~2008-04-16 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 4:24 AR5K_INT_SWBA can't generate interruption for sending beacons cao jing
2008-04-15 8:36 ` Holger Schurig
2008-04-15 8:51 ` Holger Schurig
2008-04-15 8:59 ` bruno randolf
2008-04-16 6:01 ` Jouni Malinen
2008-04-16 8:43 ` bruno randolf [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=200804161043.01769.bruno@thinktube.com \
--to=bruno@thinktube.com \
--cc=caojing.china@gmail.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
/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.