On Saturday 05 July 2008, Johannes Berg wrote: > On Sat, 2008-07-05 at 21:26 +0200, Ivo van Doorn wrote: > > On Saturday 05 July 2008, Johannes Berg wrote: > > > > > > > Hmm, in that case I have to fix something in the beacondone handler > > > > to prevent it requesting a beacon when mac80211 hasn't supplied anything > > > > yet.. > > > > > > I was working in this area... Can you take a quick look at this patch > > > and let me know what you think? > > > http://johannes.sipsolutions.net/patches/kernel/all/2008-07-05-18%3a42/mac80211-beacon-revamp.patch > > > > Patch looks good to me, it wouldn't change anything about the above since t2x00 would still > > call ieee80211_beacon_get() when the beacon wasn't provided by mac80211 yet. > > Oh, of course, I just was writing on the patch and read your mail and > replied instead of sending you another one :) > > One thing I'm worried about is the sequence numbers, but that bug is > already there... IIRC you needed software sequence numbers for your > drivers, but what about the beacons? I haven't _changed_ anything, but > IBSS beacons seem to not get a software sequence number. That problem is only in rt2400pci and rt2500pci who raise the beacon interrupt, all other drivers have the template and auto sequence numbers. But no sequence numbers for the beacons, I think that will definately cause problems for those 2 drivers. But the function ieee80211_include_sequence() is being called from within the ieee80211_beacon_get() function. Only for the Mesh it doesn't seem to be called. > > But the flags that mark what has changed is definately a good idea, > > that will prevent some redundant register writes. :) > > :) > Only once you use the flags. My patch is intentionally minimal. Not a problem, with that patch some other beaconing in the rt2x00 code will change anyway. :) 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
