On Wed, Nov 28, 2012 at 5:08 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Fri, 2012-11-23 at 12:23 -0800, Marco Porsch wrote: >> Currently the mesh sync code checks, whether peers indicate TBTT adjustment, >> but it never sets the corresponding flag itself. >> >> By setting ifmsh->tbtt_adjusting to true, it will set the corresponding field >> in the mesh configuration IE of own beacons. >> This indication will be set in the current beacon. The TBTT adjustment will be >> performed afterwards, affecting the next beacon. Thus, the first beacon with >> stable TBTT will not indicate adjustment anymore and peers will continue >> tracking the new offset. > > Ping mesh folks, does this look sane? Looks fine. The only effect (as Marco mentioned) is that the "adjusting tbtt" bit is advertised correctly in the mesh config IE. Thomas -- 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
