gpsd-dev
[Top][All Lists]
Advanced

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

Re: [gpsd-dev] Time to let the code cool down


From: Eric S. Raymond
Subject: Re: [gpsd-dev] Time to let the code cool down
Date: Mon, 18 Nov 2013 17:44:24 -0500
User-agent: Mutt/1.5.21 (2010-09-15)

Gary E. Miller <address@hidden>:
> No,  30 mSec. BIT difference.  It had been mostly 3mSec which was no where 
> near lng enough at 4800.

Ah, I see.

> > We could add a semaphore, I suppose.  Increment on each sirf_write(),
> > decrement on each ack, return an error if the user tries to trigger a
> > sirf_write() while the semaphore is nonzero.  That would never block
> > traffic. Some requests might fail.
> 
> the SiRF IV doc implies we need somthing like that.  Since it does not work
> yet that is the next thing to try.

The next question is whether older SiRFs send ACKs. If not, we need 
some way to distinguish the IVs up front.

First attempt at semaphore just pushed.  I'll test it against SiRF-II and
SiRF-IV when I get back from martial-arts class later this evening.
-- 
                <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>

Attachment: signature.asc
Description: Digital signature


reply via email to

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