Friday, September 14, 2018 6:49 PM >> What is wrong with keeping the clockIdentity the same? Isn't that the >> whole point to this exercise? >>
> I think the comment is that if ptp4l is restarted, the clock identity will > change. >Thanks, >Jake Yes, the restart is the thing here. Different port setup when restarting ptp4l may change clockIdentity. The clockIdentity should off course stay the same if you add a new port or remove an old, like you propose below. > This is what I propose: > > - stack starts up with clockIdentity as we have it now > - you add a port via custom management message; clockIdentity same > - you remove a port via custom management message; clockIdentity same > > See? > > This makes sense to me, but it does only ensure the clockIdentity during when > runtime, > and wouldn't handle the case where the application is restarted for some > reason. > Maybe we don't care about that, though. > Thanks, > Jake /Anders _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
