On Sat, Dec 08, 2018 at 11:57:44AM +0100, Robin Shamsnejad wrote: > This is not a problem for audio I/O as we don't need absolute time, > only matching clock frequencies. The problem is on the Linux slave > computer : abruptly setting the system clock to 1970 causes a lot of > problems, among them a forced filesystem check on reboot, or a need > to reset the hardware RTC.
You can fix this by changing your system's init scripts *not* to do those things. > In this use case, only audio software would need to use the PTP > clock. Would there be a way to slave another clock in the Linux > system than CLOCK_REALTIME ? In other words, is it possible to > create a separate clock, slaved to the PTP master, that would only > be used by the audio software (I'm thinking of JACK in particular) ? When using a PHC (HW time stamping), you already have a separate posix clock. You can let your applications use this PHC time directly by calling clock_gettime(). You'd have to hack jack though. HTH, Richard _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
