Date: Sun, 16 Aug 2015 08:10:41 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-stable@freebsd.org Subject: Re: 10.2: ntp update breaks DCF77 clock Message-ID: <55D03771.9000605@FreeBSD.org> In-Reply-To: <slrnmsunlo.104l.naddy@lorvorc.mips.inka.de> References: <slrnmsunlo.104l.naddy@lorvorc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --D4rco389VCFWDJxRvUfDkph6wRknH9mLL Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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. >=20 > 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. For a more timely solution[*], it looks like the ports is your best option. By default the net/ntp port disables all of the clock drivers, but allows you to configure the port to enable whatever drivers you want. If you built your own package it would be simple to get the right support compiled in. However, that won't help if you're determined to use pre-built packages only, in which case there would need to be a slave port with enabled clock drivers. That's something you could certainly argue for; This is a symptom of the current state of the ports tree -- we've switched over to pkg(8), but we're still working through a lot of changes to fully enable pkg capabilities. A lot of the functionality still only really works if you build your own ports. There are changes planned, like sub-packages and package flavours which should help, but in the case of net/ntp where clock drivers are compiled into the main binary unfortunately those won't apply. If NTP clock drivers were implemented as loadable modules it would be a lot easier... Cheers, Matthew [*] Pun unintentional. --D4rco389VCFWDJxRvUfDkph6wRknH9mLL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) iQJ8BAEBCgBmBQJV0Dd4XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkAT1bcP/2KEvDKrEAFN/viTlvPFysFB awox39wLxuR9Goil8EXMOI61+vFV88TKna6M2KbwX+KiyBJiFxMvJxrAe4wps0TV faX1lYEvN/INTXyqBqe0xd1VNIWtUomLt17ikgd7hPf26L/RA5S7UMeN22A2yS9j VFt0Z/pGnRmuMyWXspX03s+rn/UyTd9F/XxupcLcudjDIDy4fZ3KoggB0m1yWQ9e HipaJcVrOa0xHTpIQX2DU0mLtm622uNeUvb+V5amgp8emRMng+eMnu9QTNc/q8Do M5XcjyU+jHzkyVJ+a1ITFkghIQvQ1dGXTpsKKVeqt8SNErpU0JbjLpXwNGPse0q/ vCJLYuzClADhbBTICBPCSvmuNajm8SKDIMEm5JaKeTa4Ls+mgGaKlA0+zO2TQd/+ Ijm8BKhfipgcl/058CN1bs9yx6cTWYydiqJIJ0gBZPr/ob+Imcuoms83GRJAEWMK p40Dj+XestMZYhHCu4/EHn2RNHOUmkt2gDixkpH/Md4jbZHqP0do9DH0WF4J1xBd 2zYQHQbzM5ajPBOHposcQ+FIrEOQKRh2ktcsMtQyqobzKs8+knfvfi/aQTU/OJ7H 30uexP9eTWn3V5YsiyKaEeQKuc7hYLvufiO6hwzQluZ0KVWy0wKF67ocdY/IBea+ dzfmjSdpnY7r5V4fyi+r =17Iy -----END PGP SIGNATURE----- --D4rco389VCFWDJxRvUfDkph6wRknH9mLL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55D03771.9000605>