On Mon, Oct 31, 2016 at 12:17:54PM +0100, Richard Cochran wrote: > This is bug where the gloabl transportSpecific setting is being > applied to the UDS interface. I'll fix this soon.
I take this back. I thought about it some more and decided not to change this. Here is why. First of all, if you run AVB according to the standard, then you should not run phc2sys in the first place. The standard tells you to leave the local clock free running and calculate the phase and frequency numerically. So strictly speaking, you would write a program similar to phc2sys that queries TIME_STATUS_NP and uses that information to tune the system clock. [ Ok, so that is rather weak, since the end station can and should tune its PHC if it wants to. Who cares what the standard says. In fact, our gPTP.cfg doesn't even set the free_running option. But the next reason is a better one. ] Secondly, we already have UDS clients that expect the global transportSpecific flag to appear in the UDS messages. The pmc program has a command line option for this. If we change the UDS port to mask the flag away, this will break existing management clients. So I think the work around is a reasonable solution for phc2sys. If anything, phc2sys should also support the transportSpecific flag, but this can wait until we can pass a config file to it. We don't want yet another command line option, IMHO. Thanks, Richard ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
