From: Patrick Maupin <pmaupin@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: thumbgps-devel@lists.bufferbloat.net,
Andrew McGregor <andrewmcgr@gmail.com>
Subject: Re: [Thumbgps-devel] USB handshake signals and Linux
Date: Wed, 14 Mar 2012 15:09:00 -0500 [thread overview]
Message-ID: <CAPz3yKfqBy6CMKczhsFb0boNKfD-qMWgAva72fpUsJn4WRoNSA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw55jC9F4Dtsp9Nf74R3AFg8SisBZE=X_UD+i38Ckf6SEA@mail.gmail.com>
On Wed, Mar 14, 2012 at 1:57 PM, Dave Taht <dave.taht@gmail.com> wrote:
> In a private chat late last night andrew mentioned that the ftdi devices
> were extensively reprogrammable, in that they came as a usb device
> but were really, underneath, just a bunch of gpios...
Yes and no. The bandwidth associated with using them as GPIOs is
relatively high compared to using them for serial ports. They have a
lot of logic to support serial communication and also (in some cases
-- not all devices have this) some other modes like SPI, I2C, JTAG, or
CPU bus emulation.
I have personally used them in serial, parallel FIFO (a fast serial
emulation), GPIO, and JTAG modes.
next prev parent reply other threads:[~2012-03-14 20:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 10:49 Eric S. Raymond
2012-03-14 12:55 ` Ron Frazier (NTP)
2012-03-14 12:58 ` Ron Frazier (NTP)
2012-03-14 18:13 ` Patrick Maupin
2012-03-14 18:42 ` Eric S. Raymond
2012-03-14 18:57 ` Dave Taht
2012-03-14 20:09 ` Patrick Maupin [this message]
2012-03-15 3:33 ` Patrick Maupin
2012-03-15 4:23 ` Eric S. Raymond
[not found] <CAFv7OigTLhw24i+jRshv0YgLogyx_GEREAOkP7tieeH1Nr5WzA@mail.gmail.com>
2012-03-15 14:37 ` tz
2012-03-15 14:52 ` Ron Frazier (NTP)
2012-03-15 17:57 ` Eric S. Raymond
2012-03-15 18:31 ` Eric S. Raymond
2012-03-15 18:54 ` Patrick Maupin
2012-03-15 19:36 ` Eric S. Raymond
2012-03-15 19:55 ` Patrick Maupin
2012-03-15 19:14 ` tz
2012-03-15 19:50 ` 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=CAPz3yKfqBy6CMKczhsFb0boNKfD-qMWgAva72fpUsJn4WRoNSA@mail.gmail.com \
--to=pmaupin@gmail.com \
--cc=andrewmcgr@gmail.com \
--cc=dave.taht@gmail.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