You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jeeps was introduced in bb94c57 in 2002. At that time gpssend.c had a function GPS_Make_Packet, which included parameters UC data and int16 n. Presumably n is the number of unsigned characters in data.
Why is n being compared to DLE (#define DLE 0x10), which one would assume is the Data Link Escape ASCII character?
Right. That spec didn't exist (outside Olathe) at the time.
I remember there was some weirdness in the USB implementation. It's not
necessary at the bus level, but I can't remember if they faithfully
mimicked this in USB or not. So there may be some related goofy - looking
code in the USB side, too.
Jeeps was introduced in bb94c57 in 2002. At that time gpssend.c had a function GPS_Make_Packet, which included parameters UC data and int16 n. Presumably n is the number of unsigned characters in data.
Why is n being compared to DLE (#define DLE 0x10), which one would assume is the Data Link Escape ASCII character?
gpsbabel/gpsbabel/jeeps/gpssend.c
Lines 62 to 66 in bb94c57
Today this has led to a similar comparison:
gpsbabel/jeeps/gpssend.cc
Lines 61 to 64 in 66fa37e
The text was updated successfully, but these errors were encountered: