HI Jin! Are you implying that only those packets which are responded by ACK create a hardware interrupt by transmission? Sorry for the dumb question but it was a bit ambiguous for me.
And i agree with beacon things in general, broadcasts from AP are not ACKed as is the case with beacon. cheers! aneeq On Thu, Jun 24, 2010 at 2:49 PM, Jin YunYe <yunye...@gmail.com> wrote: > Hi, Aneeq > > I think some management frames, such as probe request, association > request, will be effectively "acknowledged" by probe response and > association response. > > Beacon is normally broadcasted by AP to in-range mobile stations. It > may not be a very good idea for every MS to ACK beacon frames sent by > the same AP. > > On Thu, Jun 24, 2010 at 8:41 PM, Aneeq Mahmood <its.an...@gmail.com> > wrote: > > Sorry for hijacking the thread but does the same procedure apply for > > management packets such as beacons where there is no ACk packets? > > From what i have experienced, beacon transmission is not notified by a > > Tx interrupt, or am i wrong? > > thanks > > cheers! > > > > On Thu, Jun 24, 2010 at 2:04 PM, Bob Copeland <m...@bobcopeland.com> > wrote: > >> > >> The hardware handles it completely so you won't get an rx interrupt for > >> these packets. But you will get TX completion interrupt for the packet > >> that is being ACKed when the ACK is received, and the tx status will > >> indicate success or failure. > >> > >> -- > >> Bob Copeland %% www.bobcopeland.com > >> > >> _______________________________________________ > >> ath5k-devel mailing list > >> ath5k-devel@lists.ath5k.org > >> https://lists.ath5k.org/mailman/listinfo/ath5k-devel > > > > > > _______________________________________________ > > ath5k-devel mailing list > > ath5k-devel@lists.ath5k.org > > https://lists.ath5k.org/mailman/listinfo/ath5k-devel > > > > >
_______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
