From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pmaupin@gmail.com>
Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com
	[209.85.212.175]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
	(Client CN "smtp.gmail.com",
	Issuer "Google Internet Authority" (verified OK))
	by huchra.bufferbloat.net (Postfix) with ESMTPS id D795E20027E
	for <thumbgps-devel@lists.bufferbloat.net>;
	Thu, 15 Mar 2012 11:54:20 -0700 (PDT)
Received: by wibhn6 with SMTP id hn6so8507558wib.10
	for <thumbgps-devel@lists.bufferbloat.net>;
	Thu, 15 Mar 2012 11:54:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	bh=iLyRwsD2afClOa5NqLtycV1YRlL2q7lhg93zmlgYGnU=;
	b=oAeJp447tCH4tsV/V+nD/02IA79hKXvIGfh8roVdKjAm+EF0cep//m2orydGAhmRqm
	sRxaNIvweT/35biRgC8z1uLPuT5NzRESubH8WUrkLGPOCBfPe3bT9QaZAUCcD41YBAte
	OLxFd/GRIaxv750ko5wKa5u8AdsVM0pjMFmX4CxKZYDRCPeyXNTSSV1pg3idfA1kCCC5
	YaaLQe6dxfovj4L80SS9b6+jMziR2AOQ7JpAEFDY2OUBdZowPeAxJMglK/d/tWeNqANM
	//jlTB/9kdyWbFP2/2irLNLOLcCyjfZxNFip5nTBQo76IbQ7+r7Wm4xe3uS3lB7+jqvD
	X5bQ==
MIME-Version: 1.0
Received: by 10.52.93.179 with SMTP id cv19mr5309763vdb.103.1331837658332;
	Thu, 15 Mar 2012 11:54:18 -0700 (PDT)
Received: by 10.220.140.132 with HTTP; Thu, 15 Mar 2012 11:54:18 -0700 (PDT)
In-Reply-To: <20120315183133.GC3870@thyrsus.com>
References: <CAFv7OigTLhw24i+jRshv0YgLogyx_GEREAOkP7tieeH1Nr5WzA@mail.gmail.com>
	<CAFv7Oij9uk1u_tTd_a4R4KjrA8CCApHTD-nD9ZFExy8hihYoGA@mail.gmail.com>
	<20120315183133.GC3870@thyrsus.com>
Date: Thu, 15 Mar 2012 13:54:18 -0500
Message-ID: <CAPz3yKfrDzUP=haEjsZ-Mi1m4C9Nbvw6AEDEihex3a7V-+PHXg@mail.gmail.com>
From: Patrick Maupin <pmaupin@gmail.com>
To: esr@thyrsus.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: thumbgps-devel@lists.bufferbloat.net, tz <tz2026@gmail.com>
Subject: Re: [Thumbgps-devel] USB handshake signals and Linux
X-BeenThere: thumbgps-devel@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: <thumbgps-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/thumbgps-devel>,
	<mailto:thumbgps-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/thumbgps-devel>
List-Post: <mailto:thumbgps-devel@lists.bufferbloat.net>
List-Help: <mailto:thumbgps-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/thumbgps-devel>,
	<mailto:thumbgps-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 18:54:21 -0000

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. =A0Because 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.

I don't know if Prolific has a similar program or not.