On Mon, Nov 15, 2021 at 10:38:53AM +0100, Olivier Dautricourt wrote: > > This series treats the values as static. There is no automatic > > update. The profile does not specify how to automatically calculate > > the values. On the contrary, it recommends a one time calibration > > "during network engineering stage": > > > > Overall time inaccuracy should be calculated during network > > engineering stage based on device specifications and network > > design. All time inaccuracy values used in this calculation should > > be based on the manufacturer's specified device time inaccuracy > > values, along with the source time inaccuracy of the recognized > > standard time source. > > > Ok, this part is confusing as the standard says above: > > On grandmasterTimeInaccuracy: > "This value should be updated in real time, as conditions > change" > and: > "TotalTimeInaccuracy shall be automatically incremented by TCs > and BCs" > > Suggesting that BC/TC inaccuracy should be taken into account > automaticaly.
Yes, but how? Magic ball? Wishful thinking? I say again: There is no automatic update. The profile does not specify how to automatically calculate the values. Because the profile provides only hand waving fluff, it is up to the end user to decide when and how to update the values. The present patch series allows this via management, just like for GM settings. Thanks, Richard _______________________________________________ Linuxptp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
