Re: [Linuxptp-users] Fw: clock_gettime() and clock_id (Nemo Crypto)

2022-10-31 Thread Nemo Crypto
Yes the bracket has the monotonic time. The time wasn't showing the same because I rebooted it before getting the logs.. Please see now. root@vshanmu:~# pmc -u -s /var/run/ptp4l-eth0-slave -b 0 "GET TIME_STATUS_NP" sending: GET TIME_STATUS_NP     02f052.fffe.440233-0 seq 0 RESPONSE MANAGEMENT T

Re: [Linuxptp-users] Fw: clock_gettime() and clock_id (Nemo Crypto)

2022-10-31 Thread Miroslav Lichvar
On Mon, Oct 31, 2022 at 02:00:28PM +, Nemo Crypto wrote: > MONOTONIC:964.921879908 > REALTIME:316260827.761696659 > TAI:316260827.761702962 > > During this time, at least, I was expecting that the phc2sys phc offset would > show the jump in offset which is not the case.. > phc2sys[44.221]: CL

Re: [Linuxptp-users] Fw: clock_gettime() and clock_id (Nemo Crypto)

2022-10-31 Thread Nemo Crypto
Hi Chris & Miroslav, Yes, you both are correct. I misunderstood my observation. sorry for the confusion. Both CLOCK_REALTIME(UTC) & CLOCK_TAI are only differ by the UTC offset. CLOCK_REALTIME do not experience jump due to timezone change or daylight savings adjustment change. This part is cle

Re: [Linuxptp-users] Fw: clock_gettime() and clock_id (Nemo Crypto)

2022-10-31 Thread Miroslav Lichvar
On Sun, Oct 30, 2022 at 05:50:00PM +, Nemo Crypto wrote: > Thank you Chris, this answers my question. > > I used CLOCK_REALTIME and observed the time jumping according to the timezone > change and day light saving adjustment. I think CLOCK_TAI would be the right > one to use, I will try thi