Re: ntpd 1PPS binding considered awful

2016-05-29 Thread Eric S. Raymond
Hal Murray : > There is a bug in docs/driver31.txt, Rockwell Jupiter - flag2 vs flag3 > We'll have to check the code to see what is going on. I did. There was a typo; I've fixed it. -- http://www.catb.org/~esr/";>Eric S. Raymond ___ dev

Re: ntpd 1PPS binding considered awful

2016-05-09 Thread Hal Murray
e...@thyrsus.com said: >> I think that won't turn on the kernel PLL logic. > That...sounds like a very good point. What *does* turn on the kernel PLL > logic? Including refclock 22 in the build and config? I know it can be set by NMEA and ATOM. Poking around, grep for kernel in docs/driver*tx

Re: ntpd 1PPS binding considered awful

2016-05-09 Thread Gary E. Miller
Yo Eric! On Mon, 9 May 2016 18:38:49 -0400 "Eric S. Raymond" wrote: > Gary E. Miller : > > > The Pi might be it. I have it set up to monitor four pool servers > > > with noselect. I get output like this: > > > > Whoops, don't do that. The full ntpd selection algorithm does not > > work wit

Re: ntpd 1PPS binding considered awful

2016-05-09 Thread Eric S. Raymond
Gary E. Miller : > > The Pi might be it. I have it set up to monitor four pool servers > > with noselect. I get output like this: > > Whoops, don't do that. The full ntpd selection algorithm does not work > without at least 3 seeming good chimers. That can't be right. How could you ever have

Re: ntpd 1PPS binding considered awful

2016-05-09 Thread Gary E. Miller
Yo Eric! On Mon, 9 May 2016 09:04:22 -0400 "Eric S. Raymond" wrote: > The Pi might be it. I have it set up to monitor four pool servers > with noselect. I get output like this: Whoops, don't do that. The full ntpd selection algorithm does not work without at least 3 seeming good chimers. An

Re: ntpd 1PPS binding considered awful

2016-05-09 Thread Eric S. Raymond
Hal Murray : > > e...@thyrsus.com said: > > 1. The HOWTO recipe will switch to the gpsd+ntpsd method. It's easier > >for kit-builders to understand. > > I think that won't turn on the kernel PLL logic. That...sounds like a very good point. What *does* turn on the kernel PLL logic? Includi

Re: ntpd 1PPS binding considered awful

2016-05-09 Thread Hal Murray
e...@thyrsus.com said: > 1. The HOWTO recipe will switch to the gpsd+ntpsd method. It's easier >for kit-builders to understand. I think that won't turn on the kernel PLL logic. This seems like a good opportunity for an experiment. What do you have in the way of a place to stand while can

ntpd 1PPS binding considered awful

2016-05-08 Thread Eric S. Raymond
Heads up, Mark! Significant technical decision point follows Hal Murray : > > e...@thyrsus.com said: > > It sounds like this has implications for how I should write the HOWTO > > recipe. Are you saying that with refclock 20 the source can get marked as a > > falseticker if it loses PPS for a wh