ntpsec: reference driver 38/hopf 6021

Eric S. Raymond esr at thyrsus.com
Tue Jul 5 09:32:31 UTC 2016

Martin Kotzan <m-ntp at kotzan.net>:
> On 2015-11-26 14:37, Eric S. Raymond wrote:
> >(Copied to the ntpsec devel list.)
> >
> >Martin Kotzan <m-ntp at kotzan.net>:
> >>I'd like to holler about the planned removal of driver type 38 (Hopf
> >>6021
> >>serial).
> >>
> >>This driver is still needed by current Hopf clocks connected via serial
> >>connection, so the "6021" part is probably a misnomer.
> >[...]
> >
> >Should we change the device name to just "Hopf serial"? What models other
> >than the 6021 does this cover?
> "Hopf serial" would be more more fitting for NTP, but these clocks can
> output
> about a dozen different strings. Since the hopf documentation refers to
> the string as  "Standard 6021 (hopf6021, time and date)" I would argue the
> "6021" should be kept in the description.
> All Hopf GPS and DCF77 clocks with a serial interface will emit that string:
> "All hopf units with a serial interface can provide the serial data string
> for NTP."
> http://www.hopf.com/en/article_en.html#ntpseri
> Martin

Looking over old email, I find I may have made a mistake.  A few weeks ago I
discovered that the generic driver supports the Hopf 6021 - it's subtype 12.
Accordingly, forgetting that I had received this request, I deleted the
dedicated Hopf 6021 driver.

The dedicated 6021 driver can be restored, but I would prefer not to do it
if generic subtype 12 works.  Parse drivers are smaller and better factored
than the standalone ones - the right direction is to move code into the
generic driver, not out.

Martin, would you please test that generic mode 12 on a 6021?
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

More information about the devel mailing list