On 2017-02-21 07:58, Terje Mathisen wrote:
> Erdem Ersagun wrote:
>> 28 Kasım 2016 Pazartesi 16:19:51 UTC+3 tarihinde Terje Mathisen
>> yazdı:
>>> Erdem Ersagun wrote:
I couldn't find any documents clarifying the process to apply for
a new reference clock driver.
Here in our projects
What Terje said.
If there is compelling reason to add a new refclock type, then please
open an enhacement request at bugs.ntp.org.
--
Harlan Stenn
http://networktimefoundation.org - be a member!
___
questions mailing list
questions@lists.ntp.org
http:/
Erdem Ersagun wrote:
28 Kasım 2016 Pazartesi 16:19:51 UTC+3 tarihinde Terje Mathisen
yazdı:
Erdem Ersagun wrote:
Hello,
I couldn't find any documents clarifying the process to apply for
a new reference clock driver.
Here in our projects, we use a custom time card (reference clock)
for time sy
AFAIK no new ref clock integrations are being accepted at this time. Check with
Harlen Stenn ( st...@nwtime.org ) who will know.
What is needed is an Interface Description Language to enable one driver to
handle all clocks.
Then it would only need a « refclock.conf »
> Le 21 févr. 2017 à 13:31
On 2017-02-21, Erdem Ersagun wrote:
> 28 Kasım 2016 Pazartesi 16:19:51 UTC+3 tarihinde Terje Mathisen yazdı:
>> Erdem Ersagun wrote:
>> > Hello,
>> >
>> > I couldn't find any documents clarifying the process to apply for a
>> > new reference clock driver.
>> >
>> > Here in our projects, we use a c
28 Kasım 2016 Pazartesi 16:19:51 UTC+3 tarihinde Terje Mathisen yazdı:
> Erdem Ersagun wrote:
> > Hello,
> >
> > I couldn't find any documents clarifying the process to apply for a
> > new reference clock driver.
> >
> > Here in our projects, we use a custom time card (reference clock) for
> > time
