Thanks Vedang. I stand corrected. From: Patel, Vedang <vedang.pa...@intel.com> Sent: Wednesday, March 25, 2020 6:45 PM To: Rodney Cummings <rodney.cummi...@ni.com> Cc: Michael Walle <mich...@walle.cc>; Richard Cochran <richardcoch...@gmail.com>; Erik Hons <erik.h...@ni.com>; linuxptp-devel@lists.sourceforge.net Subject: [EXTERNAL] Re: [Linuxptp-devel] [RFC V2] Add IEEE 802.1AS-2011 time-aware bridge support
Hi Rodney, Just a small correction. On Mar 25, 2020, at 3:26 PM, Rodney Cummings <rodney.cummi...@ni.com<mailto:rodney.cummi...@ni.com>> wrote: - the SYNCs are forwarded upon reception of a SYNC packet; then the correction field is updated. - there is no concept of syncLocked in the current standards. Only the new 802.1AS-REV (and I guess that will be the 802.1AS-2020?! introduces that. But even in that case, the correction field is updated based on the last received sync. So it is more a TC with some artificial update. 802.1AS-2011 supports changing portDS.logSyncInterval with a Signaling message. Linuxptp doesn't support that, which is totally fine, but we might want to support it someday. Linuxptp does support interval change request via signaling message. :) It was added as part of supporting the AVnu automotive profile in https://sourceforge.net/p/linuxptp/code/ci/630ce719fc518227d59900a66d499de836987fc2/<https://urldefense.com/v3/__https:/sourceforge.net/p/linuxptp/code/ci/630ce719fc518227d59900a66d499de836987fc2/__;!!FbZ0ZwI3Qg!68tZELo39oA1VOm_VmFMOxI7fObegy6A4QVcFoRjI5ktL06OX_CXl9W-TOEbf_iUYg$> The full series which added support can be found at: https://sourceforge.net/p/linuxptp/mailman/message/36585436/<https://urldefense.com/v3/__https:/sourceforge.net/p/linuxptp/mailman/message/36585436/__;!!FbZ0ZwI3Qg!68tZELo39oA1VOm_VmFMOxI7fObegy6A4QVcFoRjI5ktL06OX_CXl9W-TOGW3OFtnA$> Thanks, Vedang
_______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
