From: Harlan Stenn <stenn@ntp.org>
To: Reg Clemens <reg@dwf.com>
Cc: john stultz <johnstul@us.ibm.com>,
hackers@lists.ntp.org, davehart_gmail_exchange_tee@davehart.net,
Roman Zippel <zippel@linux-m68k.org>,
linux-kernel@vger.kernel.org, reg@fw.dwf.com,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [ntp:hackers] ntp-dev-4.2.5p235-RC build failure: MOD_NANO not #defined
Date: Thu, 22 Oct 2009 01:58:12 +0000 [thread overview]
Message-ID: <20091022015823.B2238C05D@mail1.ntp.org> (raw)
In-Reply-To: Message from Reg Clemens <reg@dwf.com> of "Wed, 21 Oct 2009 17:03:57 CST." <200910212303.n9LN3vFt000507@deneb.dwf.com>
> Isnt it just time to get rid of these MOD_ constructs in ntp?
Could be, but the spec says:
/*
* The following defines and structures define the user interface for
* the ntp_gettime() and ntp_adjtime() syscalls.
*
* Control mode codes (timex.modes)
*/
#define MOD_OFFSET 0x0001 /* set time offset */
#define MOD_FREQUENCY 0x0002 /* set frequency offset */
#define MOD_MAXERROR 0x0004 /* set maximum time error */
#define MOD_ESTERROR 0x0008 /* set estimated time error */
#define MOD_STATUS 0x0010 /* set clock status bits */
#define MOD_TIMECONST 0x0020 /* set PLL time constant */
#define MOD_PPSMAX 0x0040 /* set PPS maximum averaging time */
#define MOD_TAI 0x0080 /* set TAI offset */
#define MOD_MICRO 0x1000 /* select microsecond resolution */
#define MOD_NANO 0x2000 /* select nanosecond resolution */
#define MOD_CLKB 0x4000 /* select clock B */
#define MOD_CLKA 0x8000 /* select clock A */
/*
* Status codes (timex.status)
*/
#define STA_PLL 0x0001 /* enable PLL updates (rw) */
#define STA_PPSFREQ 0x0002 /* enable PPS freq discipline (rw) */
#define STA_PPSTIME 0x0004 /* enable PPS time discipline (rw) */
#define STA_FLL 0x0008 /* enable FLL mode (rw) */
#define STA_INS 0x0010 /* insert leap (rw) */
#define STA_DEL 0x0020 /* delete leap (rw) */
#define STA_UNSYNC 0x0040 /* clock unsynchronized (rw) */
#define STA_FREQHOLD 0x0080 /* hold frequency (rw) */
#define STA_PPSSIGNAL 0x0100 /* PPS signal present (ro) */
#define STA_PPSJITTER 0x0200 /* PPS signal jitter exceeded (ro) */
#define STA_PPSWANDER 0x0400 /* PPS signal wander exceeded (ro) */
#define STA_PPSERROR 0x0800 /* PPS signal calibration error (ro) */
#define STA_CLOCKERR 0x1000 /* clock hardware fault (ro) */
#define STA_NANO 0x2000 /* resolution (0 = us, 1 = ns) (ro) */
#define STA_MODE 0x4000 /* mode (0 = PLL, 1 = FLL) (ro) */
#define STA_CLK 0x8000 /* clock source (0 = A, 1 = B) (ro) */
H
prev parent reply other threads:[~2009-10-22 2:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 18:38 James Cloos
2009-10-20 19:27 ` [ntp:hackers] " Dave Hart
2009-10-20 20:45 ` john stultz
2009-10-20 23:22 ` James Cloos
2009-10-21 0:43 ` john stultz
2009-10-21 23:03 ` Reg Clemens
2009-10-22 1:58 ` Harlan Stenn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091022015823.B2238C05D@mail1.ntp.org \
--to=stenn@ntp.org \
--cc=davehart_gmail_exchange_tee@davehart.net \
--cc=hackers@lists.ntp.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reg@dwf.com \
--cc=reg@fw.dwf.com \
--cc=tglx@linutronix.de \
--cc=zippel@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome