On Thu, Apr 22, 2021 at 01:35:11PM +0000, Geva, Erez wrote: > You need to verify the ptp4l can dynamically change the master only flag.
+1 > As the 'slave only' flag does not allow set, I skip it for now. Right, and it wouldn't work if added naively. > Only priorities 1 and 2 can be changed at the moment. They do work dynamically. > However as the 'master only' is a port action and not clock action as 'slave > only', it might be easier to implement and verify. Right, many of the SET actions would require re-initializing the stack, but this isn't trivial to implement. I tried adding more SET actions some time ago, but I soon ran into corner cases in the code that spoiled everything. It is one of the weaknesses of linuxptp. As practical matter, in my own projects I simply re-start the start when the configuration changes. Although not ideal, that is easier than re-working linuxptp to properly handle each dynamic variable. Sorry, Richard _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
