From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] "gpio device" for Plan 9
Date: Tue, 31 Dec 2013 17:52:16 -0500 [thread overview]
Message-ID: <98871765283438ed6f7433aa78db438b@mikro> (raw)
In-Reply-To: <CANZw+5e7T2ubZwm9ty=wZBEeJT6hPj7EGQ49pMtoYsYsWyekGg@mail.gmail.com>
> So, in effect, a 1PPS signal would be sufficient to clock second to second?
> I suppose it could be, there would be little drift in the oscillator per
> the second.
>
> As for NTP, this has been suggested to me, and I acknowledge its place,
> certainly. However, I do not wish to tie up network resources in terms of
> clocking, and GPS provides me with an independent reference - Navsync
> CW12-TIMs can be had for $89, and do not tie up network resources. You
> could then say "Ah, but you said a 1PPS is fine... now you're saying 1PPS
> via the network isn't?" That is due to a mesh topology being used in the
> eventual network, and the bandwidth, latency and propagation issues
> inherent in such a network. I wish to dedicate the network wholly and
> solely to requisite control data traffic, not superfluous traffic like
> clocking, which may not get there in time. Certainly, mine is a complex
> undertaking, but one I think can work.
if not on the normal network, how do you plan on distributing the clock
signal?
- erik
next prev parent reply other threads:[~2013-12-31 22:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 22:04 Krystian Lewandowski
2013-12-29 22:34 ` erik quanstrom
2013-12-30 7:32 ` Skip Tavakkolian
2013-12-30 22:38 ` Shane Morris
[not found] ` <35A33F66-EF03-4659-ABA1-F25082DBFE41@gmail.com>
2013-12-31 17:46 ` Krystian Lewandowski
2013-12-31 19:18 ` erik quanstrom
2013-12-31 19:37 ` Shane Morris
2013-12-31 19:48 ` Skip Tavakkolian
2013-12-31 19:50 ` erik quanstrom
2013-12-31 20:45 ` Shane Morris
2013-12-31 22:03 ` erik quanstrom
2013-12-31 22:17 ` Shane Morris
2013-12-31 22:52 ` erik quanstrom [this message]
2013-12-31 22:57 ` Krystian Lewandowski
2013-12-31 23:16 ` Shane Morris
2013-12-31 23:35 ` Shane Morris
2014-01-01 0:04 ` Krystian Lewandowski
2014-01-01 0:12 ` Shane Morris
2014-01-01 1:12 ` Matthew Veety
2014-01-01 11:38 ` Richard Miller
2014-01-01 22:16 ` erik quanstrom
2014-02-28 23:30 ` Krystian Lewandowski
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=98871765283438ed6f7433aa78db438b@mikro \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).