Historic archive of defunct list thumbgps-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: tz <tz2026@gmail.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] USB handshake signals and Linux
Date: Thu, 15 Mar 2012 15:50:42 -0400	[thread overview]
Message-ID: <20120315195042.GC5250@thyrsus.com> (raw)
In-Reply-To: <CAFv7Oiij2z8Aaur6E+V8_YVMEOykM+upgFm+hxUE4Ej08kLFrA@mail.gmail.com>

tz <tz2026@gmail.com>:
> 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?
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

  reply	other threads:[~2012-03-15 19:51 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
2012-03-15 19:55         ` Patrick Maupin
2012-03-15 19:14     ` tz
2012-03-15 19:50       ` Eric S. Raymond [this message]
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=20120315195042.GC5250@thyrsus.com \
    --to=esr@thyrsus.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