From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from snark.thyrsus.com (static-71-162-243-5.phlapa.fios.verizon.net [71.162.243.5]) by huchra.bufferbloat.net (Postfix) with ESMTP id 44C75200370 for ; Thu, 15 Mar 2012 12:51:04 -0700 (PDT) Received: by snark.thyrsus.com (Postfix, from userid 1000) id 6A2BA40617; Thu, 15 Mar 2012 15:50:42 -0400 (EDT) Date: Thu, 15 Mar 2012 15:50:42 -0400 From: "Eric S. Raymond" To: tz Message-ID: <20120315195042.GC5250@thyrsus.com> References: <20120315183133.GC3870@thyrsus.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Eric Conspiracy Secret Labs X-Eric-Conspiracy: There is no conspiracy User-Agent: Mutt/1.5.21 (2010-09-15) Cc: thumbgps-devel@lists.bufferbloat.net Subject: Re: [Thumbgps-devel] USB handshake signals and Linux X-BeenThere: thumbgps-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list Reply-To: esr@thyrsus.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 19:51:04 -0000 tz : > The problem is that if I hook up an Arduino (on most Distros including > gpsd or even gpsd installed new), gpsd fires up and tries probing. Yes, I know. There's no help for this short of disabling GPSD autostart by udev. That would hurt a lot more people (as in, everybody who wants to just plug in a USB GPS and go) than it would help. > My argument is not with the others with unique ids (vendor/product) > but the one with the plain, default vendor/product ID that is on by > default in udev (instead of commented out with a note). You apparently don't quite get it yet (no blame, this stuff is ugly and obscure). There are *no* "unique" VID/PID pairs for GPSes. All the VID/PID pairs in gpsd.rules do is recognize USB-to-serial adapters, because that's all that can be done. GPSD has no way to know what the device on the other side of the adapter is - it starts on the premise that the thing might be a GPS, then releases the device if it fails to recognize GPS packets over the wire. > It would also be nice if it would autoconfigure which pin/pins were > used. You could enable it and then use something to figure out which > pin (or enable change on any of them?). Hm, that's an interesting idea. Enabling change on any of them would fit our design philosophy. ckuethe, are you listening? Can you think of any reason this might break something? -- Eric S. Raymond