[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] Getting the driver-switching logic right
From: |
Eric S. Raymond |
Subject: |
Re: [gpsd-dev] Getting the driver-switching logic right |
Date: |
Mon, 14 Oct 2013 18:24:48 -0400 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Andy Walls <address@hidden>:
> > 1. When you see a unique packet type for a driver with control
> > capabilities, switch to that driver. Covers EverMore binary, Garmin
> > serial binary, Geostar binary, oncore binary, Navcom binary, SiRF
> > binary, SuperStar II binary, Trimble TSIP binary, uBlox UBX binary,
> > and Zodiac binary.
>
> Does that include MT-3301 and other enhanced NMEA devices? I'm not sure
> what you mean when you say "control capabilities.
Speed switching, mode switching, sample-rate switching.
It includes the MT-3301, because the MT-3301 has a rate-switching control.
> Ignoring my hacks to make the MT-3301 driver suitable for my MT-3329
> device, the 'event_triggermatch' change is needed to switch drivers to
> the MT-3301 driver, since Generic-NMEA gets 'event_identified' first and
> the MT-3301 driver never gets activated otherwise.
Ouch. That's a bug. I think I know what causes it. I'll look into it.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>