On Fri, May 14, 2021 at 7:33 PM Richard Cochran
wrote:
>
> On Thu, May 13, 2021 at 07:31:27PM +0200, Lars Munch wrote:
> > On Sat, May 8, 2021 at 8:47 PM Richard Cochran
> > wrote:
> > >
> > > On Sat, May 08, 2021 at 02:57:30PM +0200, Lars Munch wrote:
> > >
> > > > 1. Use the time provided by g
On Thu, May 13, 2021 at 07:31:27PM +0200, Lars Munch wrote:
> On Sat, May 8, 2021 at 8:47 PM Richard Cochran
> 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
On Sat, May 8, 2021 at 8:47 PM Richard Cochran 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 simp
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.
> 2. Use libgpsd to get the time, but that adds a dependency to gpsd
No, I won't use that
My experiences of gpsd are not good. It didn’t (three years ago) have recovery
in case it got out of sync with NMEA messages. When it stopped
working, you had to kill it and restart
From: Lars Munch [mailto:l...@segv.dk]
Sent: Samstag, 8. Mai 2021 13:58
To: linuxptp-devel@lists.sourceforge
