Historic archive of defunct list thumbgps-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Patrick Maupin <pmaupin@gmail.com>
Cc: thumbgps-devel@lists.bufferbloat.net, tz <tz2026@gmail.com>
Subject: Re: [Thumbgps-devel] USB handshake signals and Linux
Date: Thu, 15 Mar 2012 15:36:11 -0400	[thread overview]
Message-ID: <20120315193610.GB5250@thyrsus.com> (raw)
In-Reply-To: <CAPz3yKfrDzUP=haEjsZ-Mi1m4C9Nbvw6AEDEihex3a7V-+PHXg@mail.gmail.com>

Patrick Maupin <pmaupin@gmail.com>:
> On Thu, Mar 15, 2012 at 1:31 PM, Eric S. Raymond <esr@thyrsus.com> wrote:
> 
> > As a workaround, GPSD picks up devices that report USB vendor-id/product-ID
> > pairs associated with USB-to-serial adapters like the PL2303 that are
> > commonly used for GPSes.  Because this is in fact the overwhelimingly
> > most common use for USB-to-serial adapters, this bodge works for almost
> > everyone almost all the time.
> 
> For what it's worth, FTDI will give you a free PID to use with their
> VID with justification.  So we could have a VID/PID that uniquely
> identifies our dongle, and/or a VID/PID that we can allow other
> manufacturers to use for any dongle using an FTDI chip and meeting the
> right specifications.

Oh, that's nice.
 
> I don't know if Prolific has a similar program or not.

I don't know either.  Might be difficult to get the vendors to implement
it if they did - their focus on cost-cutting is pretty brutal, and leads
to chop-shop engineering with results you've already seen in the Xucai
dongle.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

  reply	other threads:[~2012-03-15 19:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2012-03-15 19:55         ` Patrick Maupin
2012-03-15 19:14     ` tz
2012-03-15 19:50       ` Eric S. Raymond
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
2012-03-15  3:33     ` Patrick Maupin
2012-03-15  4:23       ` 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=20120315193610.GB5250@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=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