Hal Murray via devel writes: >> clock_var_list="name,timecode,poll,noreply,badformat,baddata,fudgetime1,fudget >> ime2,stratum,refid,flags,device,clock_var_list,refclock_ppsskew,refclock_ppsti >> me,refclock_time,ref >> clock_status,refclock_format,refclock_states,,\x0c\x0c\x0 >> 1,\x01", > > refclock_ppsskew is only in refclock_generic.
Yes, I think the idea is that there are some things common to all generic drivers and the rest will come from the specific driver you're using. > I don't know how that stuff works. Looks like there is some mechanism for > drivers to add to the list of driver variables and it's returning one too > many. Yes. > The only place where refclock_states occurrs in the code is: > tt = ap(start, LEN_STATES, tt, "refclock_states=\""); > So I don't know how that string gets into the clock_var_list list. OK, thanks for looking. I'll have to sit down to figure this out one day, but no time for that right now. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
