On Sat, May 8, 2021 at 8:47 PM Richard Cochran <richardcoch...@gmail.com> wrote: > > On Sat, May 08, 2021 at 02:57:30PM +0200, Lars Munch wrote: > > > 1. Use the time provided by gpsd to ntpshm. This can be implemented without > > dependencies to gpsd. > > Doesn't sound aweful, but not great either.
I kind of like the simplicity of this solution. No need for extra daemons to pipe the data from gpsd to ts2phc. The thing I do not like is the polling that it would have to do, but that's only a few times per second. Anything else that I have missed which is awful? Does this mean I should not waste my time implementing this as you can already now say it will not be accepted? > > I might also be able to use gpspipe and socat to get the NMEA sentences > > from gpsd to ts2phc, but that is not very elegant. > > This is best approach IMO. You can wrap gpspipe|socat in a systemd > job to get automatic restarting and logging and so on. If the > gpspipe|socat combination is too flaky to keep running, then writing a > little C or python program to read the UART and publish two sockets is > pretty easy. For the email archives; the following works as long as you do no restart anything: $ gpspipe -r | socat -u STDIN TCP4-LISTEN:9876,reuseaddr,fork,bind=127.0.0.1 and then configured ts2phc.nmea_remote_host, ts2phc.nmea_remote_port. Thanks Lars Munch _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
