http://linuxpps.org/ 2026-04-14T10:09:26+0200 http://linuxpps.org/ http://linuxpps.org/lib/tpl/dokuwiki/images/favicon.ico text/html 2018-08-30T18:24:20+0200 Anonymous (anonymous@undisclosed.example.com) http://linuxpps.org/doku.php/linuxpps_faq?rev=1535646260&do=diff LinuxPPS FAQ Q1) Running my NTPD driver I see in the log messages: [ntpd] refclock_nmea: time_pps_kcbind failed: Operation not supported Is that an implementation bug? A1) No. The function time_pps_kcbind() is defined as “optional” into RFC 2783 and, simply, LinuxPPS doesn't implement it! :) text/html 2018-08-29T15:56:43+0200 Anonymous (anonymous@undisclosed.example.com) http://linuxpps.org/doku.php/sidebar?rev=1535551003&do=diff LinuxPPS index text/html 2020-11-26T16:06:35+0200 Anonymous (anonymous@undisclosed.example.com) http://linuxpps.org/doku.php/start?rev=1606403195&do=diff LinuxPPS wiki Welcome to new LinuxPPS's wiki page! Overview LinuxPPS provides a programming interface (API) to define in the system several PPS sources. PPS means “pulse per second” and a PPS source is just a device which provides a high precision signal each second so that an application can use it to adjust system clock time. text/html 2025-02-24T10:02:51+0200 Anonymous (anonymous@undisclosed.example.com) http://linuxpps.org/doku.php/technical_information?rev=1740387771&do=diff Technical Information RFC considerations While implementing a PPS API as RFC 2783 defines and using an embedded CPU GPIO-Pin as physical link to the signal, I encountered a deeper problem: At startup it needs a file descriptor as argument for the function ''time_pps_create()''.