On Wed, Oct 03, 2018 at 08:58:51PM +0000, Maxime Lemonnier wrote: > so, if I read the doc correctly, since I want my CLOCK_REALTIME synched too > (by eth0 in my use case) I use > > ptp4l -i eth0 -i eth1 -i eth2 --boundary_clock_jbod=1 > phc2sys -a -r
Yes. > ... and all devices should use HW timestamping. I understand that I can not > use the -O -37 anymore, so how will I get UTC time on my CLOCK_REALTIME? Your TimeSever should provide TAI, and phc2sys knows how to convert from TAI to UTC based on the information provided by the TimeServer. > Can/should I force eth0 to be slaveOnly (this one is to be mastered by my > TimeServer on subnet 192,168..0.x), or should I let it it figure all this > out automatically? If the TimeServer is advertising a low clock class value, then it should just work. Otherwise just use the priority1 setting to de-prioritize the ptp4l instance. HTH, Richard _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
