[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] Updated docs on NTP segment management
From: |
Harlan Stenn |
Subject: |
Re: [gpsd-dev] Updated docs on NTP segment management |
Date: |
Sat, 07 Mar 2015 12:53:56 -0800 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 |
On 3/7/15 12:48 PM, Gary E. Miller wrote:
> Yo Harlan!
>
> On Sat, 07 Mar 2015 20:37:11 +0000
> Harlan Stenn <address@hidden> wrote:
>
>> "Gary E. Miller" writes:
>>> Harlan Stenn <address@hidden> wrote:
>>>
>>>> Your patch uses clock_gettime() to get the time for the tvc
>>>> structure.
>>>
>>> Eric supplies an alternate clock_gettime() for OS that do not have
>>> it, or that name it something else.
>>
>> Where is this? I'm not seeing it in the gpsd repo.
>
> clock_gettime.c
>
>>> Other than Windows I think the portablility fallback is now known
>>> good.
>>
>> Not to the breadth of machines that NTP runs on.
>
> Easy to fix. Got any off the top of you head?
>
>> I've also got a report of clock_gettime() not being present on some
>> Mac OSX releases.
>
> Known issue, already fixed in clock_gettime.c
>
>> I see gpsutils.c has a timestamp() function that will use
>> clock_gettime() if it's available, and gettimeofday() otherwise.
>
> Not any more.
>
> Do you have a recent git head?
I thought I did - I just re-pulled and it showed up.
>>> Also gspd has had a history of developers taking low resolution
>>> time and later using it in high resolution contexts. Put another
>>> way, a lot of speccial caing to fit the exact precision needs has
>>> been problematic, so we have been moving to just always doing
>>> things in the most precise way.
>>
>> This is all good, and it's not in the git repo I have on my machine.
>> My repo says it's up to date.
>
> Odd, I see it just fine.
>
>> And to do what you ask will require a major overhaul a short period of
>> time before a patch release to our -stable branch.
>
> Hmm, we are on the gpsd list. We are talking about gpsd, right?
No, I'm talking about the SHM patch that Eric sent me for NTP.
>> So at this moment I'm inclined to take the easy way out and get our
>> code running on lots of platforms again, knowing we can do something
>> with a local replacement for clock_gettime() down the road.
>
> We must have our wires crossed some how... That code is runnning fine
> and portably on gpsd.
Right, and see above.
--
Harlan Stenn <address@hidden>
http://networktimefoundation.org - be a member!
Re: [gpsd-dev] Updated docs on NTP segment management, Harlan Stenn, 2015/03/07
- Re: [gpsd-dev] Updated docs on NTP segment management, Gary E. Miller, 2015/03/07
- Re: [gpsd-dev] Updated docs on NTP segment management, Harlan Stenn, 2015/03/07
- Re: [gpsd-dev] Updated docs on NTP segment management, Gary E. Miller, 2015/03/07
- Re: [gpsd-dev] Updated docs on NTP segment management,
Harlan Stenn <=
- Re: [gpsd-dev] Updated docs on NTP segment management, Gary E. Miller, 2015/03/07
- Re: [gpsd-dev] Updated docs on NTP segment management, Eric S. Raymond, 2015/03/07
- Re: [gpsd-dev] Updated docs on NTP segment management, Harlan Stenn, 2015/03/07