Re: Bounding the target platforms

2017-03-01 Thread Gary E. Miller
Yo Hal! On Wed, 01 Mar 2017 15:24:08 -0800 Hal Murray wrote: > RFC1589 describes an in-kernel PLL that synchronizes the system clock to an > external PPS signal. RFC1589 is what the kernel did in 1995. Mills had input to an update to the in kernel PLL in 1999. I

Re: Bounding the target platforms

2017-03-01 Thread Hal Murray
e...@thyrsus.com said: > The immediate issue is whether we can drop RFC1589 support in favor of > RFC2783. RFC1589 describes an in-kernel PLL that synchronizes the system clock to an external PPS signal. RFC2783 describes the API for user code to read the time stamps for a PPS signal that the

Re: Bounding the target platforms

2017-02-27 Thread Eric S. Raymond
Hal Murray : > > e...@thyrsus.com said: > > So let's drop back to two questions: > > 1. What platforms do we care about supporting in client mode (doesn't need > > PPS)? > > I don't see how you jumped from client mode to not needing PPS. > > I'm not even sure what

Re: Bounding the target platforms

2017-02-27 Thread Hal Murray
e...@thyrsus.com said: > So let's drop back to two questions: > 1. What platforms do we care about supporting in client mode (doesn't need > PPS)? I don't see how you jumped from client mode to not needing PPS. I'm not even sure what "client mode" means. Does it mean no clients? aka it is a

Bounding the target platforms

2017-02-26 Thread Eric S. Raymond
Mark: heads up! Policy issue. Gary E. Miller : > > No, it's still here, if you mean hardpps amd RFC1589 support. Though > > I didn't know that until today - it's amost completely undocumented, > > you have notice the hint dropped by the meaning of flag3 and then read > > source