On Wed, May 17, 2017 at 04:08:53PM +0200, Miroslav Lichvar wrote: > On Wed, May 17, 2017 at 03:58:40PM +0200, Petr Kulhavy wrote: > > + case TLV_DOMAIN: > > + mtd = (struct management_tlv_datum *) tlv->data; > > + c->dds.domainNumber = mtd->val; > > + *changed = 1; > > + respond = 1; > > + break; > > Shouldn't this also reset the state of the clock?
Yes, each port of the clock would have to start again in PS_INITIALIZING and listen for announce message in the new domain. Alternatively, you could let the ports keep track of multiple domains in parallel, allowing more seamless domain switching, but that of course is much more work. [ The 'changed' flag only causes a state decision event, but that would be wrong here because the change in domain invalidates the ports' foreign master records. ] Thanks, Richard ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
