[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-dev] [PATCH] Time Service HOWTO: Clarify state of RFC2783 on N

From: Greg Troxel
Subject: Re: [gpsd-dev] [PATCH] Time Service HOWTO: Clarify state of RFC2783 on NetBSD.
Date: Tue, 26 Aug 2014 16:02:30 -0400
User-agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.4 (berkeley-unix)

"Gary E. Miller" <address@hidden> writes:

>> That's not correct.  NetBSD has had RFC2783 support (really, a late
>> version of the internet draft the became RFC2783) since about 1999.
>> The only recent change was to hook it into usb-serial devices.  
> So, we agree, added lately.  At least for gpsd purposes.

huh?  For real serial ports, it's been there about 15 years (and working
with ntpd directly).  It's only the odd case of USB-serial PPS that is

> As you said RFC2783 does not specify an API, so assumptions (reverse 
> engineering) is required to make it work.  NetBSD just made different
> assumptions to complete what RFC2783 mmissed.

I don't think that's true, or at least we haven't figured that out.  In
any specification, some things are left unclear.  Correct code may only
rely on behavior that is controlled by the specification.  We see this
with POSIX specs all the time.

>>  So certainly we should fix it -- my comment was meant
>> to note that it does not work, not that it never will.  Perhaps that
>> should be clearer.
> How about we skip the doc change, and just add to the TODO?

Because esr added a doc change which was wrong, and that needs to be

Attachment: pgpdbohKv7EaG.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]