Historic archive of defunct list thumbgps-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: thumbgps-devel@lists.bufferbloat.net, gpsd-dev@nongnu.org
Subject: Re: [Thumbgps-devel] [gpsd-dev] PPS over USB
Date: Tue, 1 May 2012 23:33:45 -0400	[thread overview]
Message-ID: <20120502033345.GA11913@thyrsus.com> (raw)
In-Reply-To: <CAA93jw6LbYvzoN4_B7EEPdBBc6NoOC9oxkdkXK8__UUPHjV3yw@mail.gmail.com>

Dave Taht <dave.taht@gmail.com>:
> I'm a little confused.
> 
> There are two threads going by today. One is about a sirfIII and the
> other a ublox 6
> 
> I have been assuming they are one and the same, but perhaps I'm confused.

You are.  The first set of prototypes, from UniTraq, were SiRF-III + CP2101.
These won't do - turns out the CP2101 driver can't wait on a handshake state 
change because the vendor never released enough programnming information.

Gary is talking about the second set of prototypes, from NaviSys.
That's the uBlox + PL2303 device.  It works.  The next step is to
get them into volume production.

> Secondly an item that has not been looked into much is the quality of
> the antennas, or the quality of the clock source when only a single
> sat is available....

Quality of antenna will matter for the device's ability to function in
weak-signal conditions, e.g. indoors.  Clock time should be OK even with
a single sat - multiple birds are needed for the spherical trig to compute
position, but atomic time you get directly from each sat sample.

> Thirdly, wow.... when can I get one of these puppies to play with?

Gary has three.  He's keeping one and sending me the second.  Since OpenBSD 
has no TICMIWAIT, Chris Kuethe is out of contention for the third and it
should logically go to you.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

  parent reply	other threads:[~2012-05-02  3:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120501151435.4a6a5373.gem@rellim.com>
2012-05-01 22:16 ` [Thumbgps-devel] Fwd: " Dave Taht
2012-05-02  1:40 ` [Thumbgps-devel] " Dave Taht
2012-05-02  3:07   ` Jim Thompson
2012-05-02  3:33   ` Eric S. Raymond [this message]
2012-05-02  7:58     ` Hal Murray
2012-05-06 21:28       ` Eric S. Raymond
2012-05-02 11:09     ` tz
     [not found]       ` <20120502131310.7dd7f799.gem@rellim.com>
2012-05-02 20:33         ` tz
2012-05-02 21:19         ` Hal Murray
2012-05-02 21:43           ` tz
2012-05-02 13:40     ` Ron Frazier (NTP)
     [not found]       ` <20120502124227.28ef9fa6.gem@rellim.com>
2012-05-03  4:07         ` Ron Frazier (NTP)
2012-05-06 22:09       ` Eric S. Raymond
     [not found] ` <4FA43068.2080606@wildgooses.com>
     [not found]   ` <20120504160455.4514ac26.gem@rellim.com>
     [not found]     ` <20120506214138.GB14699@thyrsus.com>
     [not found]       ` <4FA6F396.70307@tmsw.no>
     [not found]         ` <4FA7BDF1.7030708@wildgooses.com>
     [not found]           ` <4FA7CFB2.9080807@tmsw.no>
     [not found]             ` <4FA7E197.9010902@wildgooses.com>
     [not found]               ` <20120507205843.GA21259@thyrsus.com>
2012-05-07 21:14                 ` Dave Taht
2012-05-07 21:52                   ` Eric S. Raymond

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=20120502033345.GA11913@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=dave.taht@gmail.com \
    --cc=gpsd-dev@nongnu.org \
    --cc=thumbgps-devel@lists.bufferbloat.net \
    /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