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] Raspberry PI on Piday; better yet, generate our own system tick with a PPS synced PLL
Date: Wed, 14 Mar 2012 13:22:22 -0500	[thread overview]
Message-ID: <CAPz3yKcu14vxYLGpAAPtkhXpiYLaGG3-pgzj1ALhM2Cehgg0WQ@mail.gmail.com> (raw)
In-Reply-To: <CAFv7Oihg27gtamyS-qigLstNW3iEJnSS5JPsbXF4717f93UhLg@mail.gmail.com>

On Wed, Mar 14, 2012 at 12:59 PM, tz <thomas@mich.com> wrote:

> The ethernet port is USB based and has a USB connector,

Hm, yet more latencies to characterize.  If one of the USB ports is
OTG, maybe we could just use a Linux gadget device interface and have
this connect to the router through USB?

> Better yet, we can move the system tick itself off to a GPIO pin
> causing an interrupt, and use a PLL frequency multiplier that syncs
> exactly to 100x (or 1000x) the PPS.  The PPS could be a second
> interrupt if there was no other easy way to indicate the UTC boundary
> from the other pulses.  The GPIO interrupt can sample the internal
> clock and do what it needs for the sub-tick timing.  I don't know
> which other peripherals, but maybe they could read the sub-tick or
> even the "time of day in microseconds" from our system over I2C or
> SPI.
>
> This could be a fairly simple circuit (worries about noise, drift...),
> or there's a chip...

Yes, there are lots of chips available for this sort of thing.
Probably don't need anything too fancy.

  reply	other threads:[~2012-03-14 18:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 17:59 tz
2012-03-14 18:22 ` Patrick Maupin [this message]
2012-03-14 19:46 ` Ron Frazier (NTP)

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=CAPz3yKcu14vxYLGpAAPtkhXpiYLaGG3-pgzj1ALhM2Cehgg0WQ@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