| Re: [chrony-users] SatPulse: server-oriented alternative to gpsd for chrony |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: James Clark <jjc@xxxxxxxxxx>
- Subject: Re: [chrony-users] SatPulse: server-oriented alternative to gpsd for chrony
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 23 Apr 2026 16:09:00 +0200
- Cc: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1776953349; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=KMj7k68KgiUefQKFkQIDCuDFiyU82zMBN8xmVifyntE=; b=WZDhai/yCUlKDGn4my94E9jh0F1plZlI/pnP6z2RsGWzX8KL701cevOSStjVsTPZPa0Ze3 49e5n1BIRGVhbHZFWpEw3jON9x0lhpU5RGxtFvADd25WsjcSa2tpUPypFfq3qxpUlfiXS+ DocfF0PQrsosuru4egurmjvYyFEholM=
On Thu, Apr 23, 2026 at 08:30:27PM +0700, James Clark wrote:
> I think this is because the module is connected using its I2C port and I
> wasn't generating the right port-dependent config key in one case. I have
> pushed a fix that I hope will fix it.
Both issues are fixed now. Thanks!
Looking at the changed defaults, I think it was the message timing
that was too unstable, possibly due to the I2C communication being too
slow and buffering in the driver. If too many messages are enabled, it
can overflow to the next second, at least with NMEA.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.