On Mon, Sep 03, 2018 at 01:49:47PM +0200, Michael Walle wrote: > It's an implementation detail (in hardware, so I can't do anything about it) > of the scheduler, that it has to be restarted if there was a clock jump. And > additionally, if there is no grandmaster anymore, we should stop the > scheduler altogether. All this, I cannot do today without patching linuxptp. > So I thought it would be a good idea to have some hooks inside linuxptp > which can take care of these tasks (and is easy to use and extendable).
So both of those events, 1. clock jump 2. loss of GM are good candidates for UDS notification. I can imagine other scenarios that would need those. 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
