Return-path: Received: from emh03.mail.saunalahti.fi ([62.142.5.109]:33057 "EHLO emh03.mail.saunalahti.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750786AbYDPGCz (ORCPT ); Wed, 16 Apr 2008 02:02:55 -0400 Date: Wed, 16 Apr 2008 09:01:09 +0300 From: Jouni Malinen To: bruno randolf Cc: Holger Schurig , linux-wireless@vger.kernel.org, cao jing Subject: Re: AR5K_INT_SWBA can't generate interruption for sending beacons Message-ID: <20080416060109.GG15053@jm.kir.nu> (sfid-20080416_070259_898655_F168468E) References: <9f33c5230804142124g3c8f4a0ai28a6b5117e1034c9@mail.gmail.com> <200804151036.55216.hs4233@mail.mn-solutions.de> <200804151059.06119.bruno@thinktube.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <200804151059.06119.bruno@thinktube.com> Sender: linux-wireless-owner@vger.kernel.org List-ID: 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. -- Jouni Malinen PGP id EFC895FA