Date: Wed, 27 Nov 2019 01:17:31 +0200 From: Stefan Parvu <sparvu@kronometrix.org> To: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: rpi3 clock drift Message-ID: <A9CDA147-01A1-4A5B-8270-9F986847EA64@kronometrix.org> In-Reply-To: <486c0bc46deeefb8338f50fe6dfdf7951786e56c.camel@freebsd.org> References: <MWHPR06MB3134CD05551D36CC3B45D368AA450@MWHPR06MB3134.namprd06.prod.outlook.com> <c5942861c2aa0929239e59a000ce76407f4fd191.camel@freebsd.org> <MWHPR06MB31341D8CB3BBF98153B55A74AA450@MWHPR06MB3134.namprd06.prod.outlook.com> <486c0bc46deeefb8338f50fe6dfdf7951786e56c.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>=20 > Can someone else with an rpi3 (which keeps good time) confirm that > that's the usual number? this is slightly different model: rpi3+ . I think it does use a = different SOC than rpi3. krmx@k1:~ % sysctl kern.timecounter=20 kern.timecounter.fast_gettime: 1 kern.timecounter.tick: 1 kern.timecounter.choice: ARM MPCore Timecounter(1000) dummy(-1000000) kern.timecounter.hardware: ARM MPCore Timecounter kern.timecounter.alloweddeviation: 5 kern.timecounter.stepwarnings: 0 kern.timecounter.tc.ARM MPCore Timecounter.quality: 1000 kern.timecounter.tc.ARM MPCore Timecounter.frequency: 19200000 kern.timecounter.tc.ARM MPCore Timecounter.counter: 3645432288 kern.timecounter.tc.ARM MPCore Timecounter.mask: 4294967295 Stefan=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A9CDA147-01A1-4A5B-8270-9F986847EA64>