On Wednesday 09 July 2008 16:04:50 Ivo van Doorn wrote: > On Wednesday 09 July 2008, Michael Buesch wrote: > > On Wednesday 09 July 2008 15:11:45 Ivo van Doorn wrote: > > > Currently only beacons generated in AP mode have the software > > > sequence number inserted. This means IBSS and Mesh mode are broken > > > for all hardware that require software sequence numbers. > > > > Does software seq numbering even work at all? > > What about packets that get sent between the driver requested the > > beacon and the driver does actually queue it? > > For rt2x00 the beacon is requested and queued within interrupt context Well, another CPU could be in progress of walking down the mac80211 TX code and aquire a sequence number in the meantime before you requested the beacon. However that frame will be blocked by your driver locks, so the two seq numbers of the beacon and the other frame will be swapped, as the driver will queue the beacon first. -- Greetings Michael. -- 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
