|
View:
New views
2 Messages
—
Rating Filter:
Alert me
|
|
|
2.40dev/SVN-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 Yo Eric! I had a chnace to take a quick look at the Garmin Serial binary driver in the latest 2.40dev. It looks like something simple got unhinged, but not sure where. here is the -D 6: gpsd: /dev/ttyS0 is known to be Garmin Serial gpsd: /dev/ttyS0 is known to be Garmin Serial gpsd: /dev/ttyS0 is known to be Garmin Serial gpsd: /dev/ttyS0 is known to be Garmin Serial gpsd: /dev/ttyS0 is known to be Garmin Serial gpsd: /dev/ttyS0 is known to be Garmin Serial gpsd: /dev/ttyS0 is known to be Garmin Serial gpsd: /dev/ttyS0 is known to be Garmin Serial gpsd: Garmin n= 0x46\x0a 1033409ca288440021914165a04741b4af524101008078e7ffffa7b34049a2622f4b9de83f2404858b3cf000c00000000000000000000000002f16a1410f00381c00005c1003 gpsd: /dev/ttyS0 is known to be Garmin Serial gpsd: <= GPS: \x103@\xfff\xfff\xfffDgpsd: unknown sentence: "\x103@\xfff\xfff\xfffD" So the bit stream is detected. The packet is accepted and discarded in packet.c on line 1192: packet_accept(lexer, GARMIN_PACKET); packet_discard(lexer); But the germin parser garmin_ser_parse() is never called. Any idea where I should look for that not happening? RGDS GARY - --------------------------------------------------------------------------- Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701 gem@... Tel:+1(541)382-8588 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFK0TVcBmnRqz71OvMRAnsxAKC6FB2MckuxIfqUPp/TY4hOJ0itIQCgsyuM XWpSnF/xeYcyNC6Y0/owNl0= =aze6 -----END PGP SIGNATURE----- _______________________________________________ Gpsd-dev mailing list Gpsd-dev@... https://lists.berlios.de/mailman/listinfo/gpsd-dev |
|
|
Re: 2.40dev/SVNGary E. Miller <gem@...>:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Yo Eric! > > I had a chnace to take a quick look at the Garmin Serial binary > driver in the latest 2.40dev. It looks like something simple got unhinged, but not sure where. > > here is the -D 6: > > gpsd: /dev/ttyS0 is known to be Garmin Serial > gpsd: /dev/ttyS0 is known to be Garmin Serial > gpsd: /dev/ttyS0 is known to be Garmin Serial > gpsd: /dev/ttyS0 is known to be Garmin Serial > gpsd: /dev/ttyS0 is known to be Garmin Serial > gpsd: /dev/ttyS0 is known to be Garmin Serial > gpsd: /dev/ttyS0 is known to be Garmin Serial > gpsd: /dev/ttyS0 is known to be Garmin Serial > gpsd: Garmin n= 0x46\x0a 1033409ca288440021914165a04741b4af524101008078e7ffffa7b34049a2622f4b9de83f2404858b3cf000c00000000000000000000000002f16a1410f00381c00005c1003 > gpsd: /dev/ttyS0 is known to be Garmin Serial > gpsd: <= GPS: \x103@\xfff\xfff\xfffDgpsd: unknown sentence: "\x103@\xfff\xfff\xfffD" > > So the bit stream is detected. The packet is accepted and discarded in > packet.c on line 1192: > packet_accept(lexer, GARMIN_PACKET); > packet_discard(lexer); > > But the germin parser garmin_ser_parse() is never called. Any idea where > I should look for that not happening? Yes. Near line 50 of drivers, where it says: /* * Dispatching on Garmin packets here causes a nasty configure * loop. It's not clear this is the right way to break the * loop or whether it merely evades the problem and breaks * autoconfiguration, but it will have to do until a Garmin * expert can grok the problem better. */ Alas for you, you're the Garmin expert... -- <a href="http://www.catb.org/~esr/">Eric S. Raymond</a> _______________________________________________ Gpsd-dev mailing list Gpsd-dev@... https://lists.berlios.de/mailman/listinfo/gpsd-dev |
| Free embeddable forum powered by Nabble | Forum Help |