Re: 10.2: ntp update breaks DCF77 clock
Cy Schubert <Cy.Schubert <at> komquats.com>
2015-08-17 05:49:57 GMT
In message <1439744220.242.87.camel <at> freebsd.org>, Ian Lepore writes:
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: 7bit
> On Sun, 2015-08-16 at 08:10 +0100, Matthew Seaman wrote:
> > On 15/08/2015 16:46, Christian Weisgerber wrote:
> > > The ntp code is not very transparent, but I think the root cause
> > > are the ntp/config.h changes that came with the 4.2.8p3 update. A
> > > number of previously disabled obscure clock drivers were enabled,
> > > but crucially CLOCK_RAWDCF was disabled, and this is the PARSE
> > > subdriver needed to use the popular DCF77 serial receivers.
> > >
> > > Frankly, it looks like we used to have a carefully considered
> > > selection of clock drivers which has been blindly splattered with
> > > the upstream defaults in the last update.
> > Hmmm.... I suggest raising a PR with patches to revert the changes in
> > the set of enabled clock drivers (or merge with the current list). It's
> > not going to get you a working DCF77 receiver in a -RELEASE version any
> > time soon, I'm afraid, as you'll have to wait until the next release for
> > the changes to percolate down, but having a sensible list of enabled
> > clock drivers in base is definitely a good move.
> I wonder: is there a reason to not enable all (or most of) the refclocks
> in base and in ports? Well, at least all the ones that build on
> freebsd... a disturbing number of them fail to compile because they