This series addresses the mismatch between the slaveOnly BMC logic from the 1588 standard and the expected gmCapable behavior from 802.1AS. That latter standard does not have slave only nodes, but rather all nodes must send announce messages.
The basic idea is to just use the normal BMC state machine and simply avoid sending sync messages, while letting the announce messages out. Thanks, Richard Richard Cochran (3): Introduce the gmCapable flag for use with 802.1AS clocks. Inhibit sync messages from unwilling 802.1AS ports. Add a configuration file option for the 802.1AS gmCapable flag. clock.c | 7 +++++++ clock.h | 8 ++++++++ config.c | 6 ++++++ ds.h | 1 + gPTP.cfg | 2 +- port.c | 28 ++++++++++++++++++++++++++++ ptp4l.8 | 7 +++++++ ptp4l.c | 9 ++++++++- 8 files changed, 66 insertions(+), 2 deletions(-) -- 1.7.10.4 ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ Linuxptp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
