On Sunday 03 February 2008, Guy Cohen wrote: > On 2/2/08, Ivo van Doorn <ivdoorn@xxxxxxxxx> wrote: > > On Saturday 02 February 2008, Tomas Winkler wrote: > > > 4965 has 4 queues which are used for regular WMM. Only 11 queues > > > might be used for aggregation, but in AP mode we might map one of the > > > queues to after beacon multicast traffic. > > > > Just out of interest, and I don't know about the iwl4965 driver specifics, > > but how will you make sure those frames are send after the beacon? > > Does the beacon trigger an interrupt after each interval which allows you to queue > > the frames or is some other approach used? > > For iwl4965, mcast frames are queued into a separate HW TX FIFO (no > need to buffer at the host). Beacon periodic transmission and > controling the TX of mcast frames from the mcast FIFO are all timely > done in real-time by the device. Thanks for the explanation. Ivo - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
