Date: Thu, 16 Dec 1999 13:35:23 -0700 From: Nate Williams <nate@mt.sri.com> To: Warner Losh <imp@village.org> Cc: nate@mt.sri.com (Nate Williams), "FreeBSD Current Users' list" <freebsd-current@FreeBSD.ORG> Subject: Re: HEADSUP: ntp4 to replace xntpd Message-ID: <199912162035.NAA20788@mt.sri.com> In-Reply-To: <199912162032.NAA73759@harmony.village.org> References: <199912161810.LAA19919@mt.sri.com> <Pine.BSF.4.05.9912160934230.23583-100000@semuta.feral.com> <16818.945366687@critter.freebsd.dk> <199912162032.NAA73759@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> : You may not know the answer to this, but it's worth a shot. Wht kind of > : accuracy can we expect using 'cheap' off-the-shelf GPS receivers? > > We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap > gps receiver + atomic clock on a i486 class machine. I've got the cheap gps receiver (Garmin 12XL), but what do you mean by an 'atomic clock'? Should the GPS receiver's NMEA messages be adequate enough to do the job? However, all I need is ms accuracy, so anything below 500us is good enough for me. > The clock > doesn't want to sync more closely than that, likely due to the large > jitter in the 8254 timing device, so the atomic clock is a bit of a > waste for this part of our application (there are others it is needed > for). With a pentium class machine and w/o the atomic clock > "backing", I'd say you could easily get into the sub-micro second > range. I've got a 486, although running the antenna to an outside window might get exciting. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912162035.NAA20788>