From: Patrick Maupin <pmaupin@gmail.com>
To: tz <tz2026@gmail.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] Project clarification
Date: Tue, 13 Mar 2012 23:36:12 -0500 [thread overview]
Message-ID: <CAPz3yKcTbEJFU4NaMsHjBDGkMHLcLKF8BvkD-LHdwmpojgNMiA@mail.gmail.com> (raw)
In-Reply-To: <CAFv7Oig842U9MYMS0hgBFRnAK3-dbqj85NQGTYaEUWFQx6idZg@mail.gmail.com>
On Tue, Mar 13, 2012 at 10:05 PM, tz <tz2026@gmail.com> wrote:
> We could send an event OUT the USB host and timestamp it at the
> device, returning when it saw it - this might be more accurate if this
> is more granular than polling.
I was definitely thinking of this when thinking of building the
FPGA-based timestamp-everything unit. You're right that if we're
willing to write USB device firmware, a lot of opportunities to gain
tighter tolerances present themselves. This would be even more true
if we pick a highspeed device.
Another simple thing we could do with basic serial units is to loop
back RTS to CTS so you can calculate round-trip time to put an upper
bound on inbound delay.
If we really want to consider our own firmware, we might consider
something like nuttx running on either an Atmel part or an NXP
LPC3131. Olimex has an NXP development board for $90.
next prev parent reply other threads:[~2012-03-14 4:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 21:46 Mike Hord
2012-03-13 23:06 ` Eric S. Raymond
2012-03-13 23:30 ` tz
2012-03-14 1:18 ` Eric S. Raymond
2012-03-14 1:10 ` Dave Taht
2012-03-14 1:28 ` Ron Frazier (NTP)
2012-03-14 1:53 ` Eric S. Raymond
2012-03-14 3:08 ` Dave Taht
2012-03-14 3:42 ` Dave Taht
2012-03-14 4:02 ` Ron Frazier (NTP)
2012-03-14 4:32 ` Eric S. Raymond
2012-03-14 12:44 ` tz
2012-03-14 2:28 ` tz
2012-03-14 2:46 ` Dave Taht
2012-03-14 3:05 ` tz
2012-03-14 4:36 ` Patrick Maupin [this message]
2012-03-14 5:00 ` 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=CAPz3yKcTbEJFU4NaMsHjBDGkMHLcLKF8BvkD-LHdwmpojgNMiA@mail.gmail.com \
--to=pmaupin@gmail.com \
--cc=thumbgps-devel@lists.bufferbloat.net \
--cc=tz2026@gmail.com \
/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