Re: DCF77 driver seems to be broken

Achim Gratz writes: > Eric S. Raymond writes: >> I'd revert this, but I didn't understand it well enough to avoid breaking it. >> Can you supply a fix patch? >> >> If not, file an issue and I'll give it a try. > > I'll first have to understand what all the original functions were doing > and then

Re: DCF77 driver seems to be broken

Yo Achim! On Sat, 18 Feb 2017 22:15:56 +0100 Achim Gratz wrote: > Gary E. Miller writes: > > There is nothing in C++, as defined by Stroustrup, that you can not > > do in C. > > You know, I've actually used Cfront and read all of Stroustrups books, > so please spare me

Re: DCF77 driver seems to be broken

Yo Achim! On Sat, 18 Feb 2017 21:30:33 +0100 Achim Gratz wrote: > Eric S. Raymond writes: > > I'd revert this, but I didn't understand it well enough to avoid > > breaking it. Can you supply a fix patch? > > > > If not, file an issue and I'll give it a try. > > I'll first

Re: DCF77 driver seems to be broken

Eric S. Raymond writes: > I'd revert this, but I didn't understand it well enough to avoid breaking it. > Can you supply a fix patch? > > If not, file an issue and I'll give it a try. I'll first have to understand what all the original functions were doing and then what the replacements do

Re: DCF77 driver seems to be broken

Achim Gratz : > Achim Gratz writes: > > This bisects to 96fff4a, although I have a hard time understanding why. > > Some of that seems to have been "prepared" in the commits running up to > > this. Anyway, the DCF77 driver thinks that each second is the last one > > in the

Re: DCF77 driver seems to be broken

Achim Gratz writes: > This bisects to 96fff4a, although I have a hard time understanding why. > Some of that seems to have been "prepared" in the commits running up to > this. Anyway, the DCF77 driver thinks that each second is the last one > in the minute after this commit landed. The latter

Re: DCF77 driver seems to be broken

Achim Gratz writes: > Was any work done on the parse refclock driver in the last half year or > so? It seems that the DCF77 driver based on it stopped working and the > symptoms are that the timecode is always just a single character. I'll > try to bisect that later, but maybe someone already

DCF77 driver seems to be broken

Was any work done on the parse refclock driver in the last half year or so? It seems that the DCF77 driver based on it stopped working and the symptoms are that the timecode is always just a single character. I'll try to bisect that later, but maybe someone already knows where this was