Historic archive of defunct list thumbgps-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Patrick Maupin <pmaupin@gmail.com>
To: tz <thomas@mich.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] Build vs. modify vs. what should we be doing anyway?
Date: Mon, 12 Mar 2012 16:27:56 -0500	[thread overview]
Message-ID: <CAPz3yKeiZbSPLF+L1n7YQtNkUB_1NVGwZSs-wzdRP-n_tPZ9Hw@mail.gmail.com> (raw)
In-Reply-To: <CAFv7OigwG=YhXbg1Jek=nP=uLhxh4Xpt0gOjLowJY0sVjxZkOA@mail.gmail.com>

On Mon, Mar 12, 2012 at 4:18 PM, tz <thomas@mich.com> wrote:

> The board is probably minimum 4 layer.

The main board could easily be 2 layers, because the GPS is done in a
surface mount module that mounts on the main board.  Pictures here:

http://www.geekzone.co.nz/forums.asp?forumid=80&topicid=60005

> The prolific is 28 pin ssop with scattered power and ground pins.

There's apparently an 8 pin variant -- check the picture...

> GPS chips (except for highly integrated modules) are worse as far as
> the pins you need to get to the right places.

Right -- you ought to be able to use modules for this quantity.

  parent reply	other threads:[~2012-03-12 21:27 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-10 18:02 Patrick Maupin
2012-03-12 21:03 ` Eric S. Raymond
2012-03-12 21:18   ` tz
2012-03-12 21:26     ` Eric S. Raymond
2012-03-12 21:28       ` Patrick Maupin
2012-03-12 21:39         ` Eric S. Raymond
2012-03-12 22:10           ` Patrick Maupin
2012-03-12 22:23             ` tz
2012-03-12 22:33               ` Patrick Maupin
2012-03-13  2:29               ` Ron Frazier (NTP)
2012-03-13  2:39                 ` Chris Kuethe
2012-03-12 22:45             ` Eric S. Raymond
2012-03-12 23:01               ` Dave Taht
2012-03-13  1:43                 ` Eric S. Raymond
2012-03-13  2:04                   ` Chris Kuethe
2012-03-13  2:13                     ` Eric S. Raymond
2012-03-13  2:40                       ` Dave Taht
2012-03-13  2:53                         ` Chris Kuethe
2012-03-13  4:54                         ` Eric S. Raymond
2012-03-13 13:23                           ` Dave Taht
2012-03-13 14:35                             ` tz
2012-03-13 16:04                             ` Eric S. Raymond
2012-03-13 16:22                               ` tz
2012-03-13  2:38                 ` Ron Frazier (NTP)
2012-03-13  2:42                   ` Chris Kuethe
2012-03-13  3:00                     ` Ron Frazier (NTP)
2012-03-13  3:04                       ` Dave Taht
2012-03-13  3:06                         ` Chris Kuethe
2012-03-13  3:16                           ` Dave Taht
2012-03-13  3:31                             ` Chris Kuethe
2012-03-13  4:49                               ` Dave Taht
2012-03-13  4:55                               ` Eric S. Raymond
2012-03-13  4:16                     ` Eric S. Raymond
2012-03-12 21:40         ` tz
2012-03-12 21:27     ` Patrick Maupin [this message]
2012-03-12 21:22   ` Patrick Maupin
2012-03-12 21:37     ` Eric S. Raymond
2012-03-12 21:45       ` Patrick Maupin
2012-03-12 22:02         ` 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=CAPz3yKeiZbSPLF+L1n7YQtNkUB_1NVGwZSs-wzdRP-n_tPZ9Hw@mail.gmail.com \
    --to=pmaupin@gmail.com \
    --cc=thomas@mich.com \
    --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