igotU mini GPS datalogger (navman/non-standard usb-serial)

[Paul Sladen]

This matchbox-sized GPS logger presents a non-standard serial point.

There is a single incoming endpoint 0x81; reading from this gets you NMEA
sentences[4]---so the USB ID (0df7:0900) was added to to the 'navman' module
back in March 2009.[0] This gets you _live_ GPS data, but not access to the
flash/datalog (which is what makes the device useful/interesting!).

Somebody else later got some traces[1] from the supplied Win32
software/driver and the outgoing writes to the device are done via
USB control messages; eg:

   usb_control_msg(type=0x21, req=0x09, value=0x0200, index=0, length <= 8)

   //  req 0x09 == USB_REQ_SET_CONFIGURATION (?)
   // type 0x21 == USB_TYPE_VENDOR | USB_RECIP_INTERFACE | USB_ENDPOINT_OUT ?

This allows reading/writing/fetching various registers/flash blocks.

That is working to a point from userspace; the ideal might be to just have
the kernel expose a standard bi-directional serial port (the current
'navman.ko' currently silently drops out-going writes) and let
userspace/gpsbabel write to that, thus still allowing NMEA dumping to work
out of the box like any other GPS and to add the rest to gpsbabel.

In terms of similarly accessed hardware, the closest I found---using
equivalent write method (so likely to be the same usb<->serial chip) is a
proposed 'usb/misc/phidgetservo.c' driver[2] that later ended up in-tree as
a whole suite of phidget*.  Some "iMON VFD/LCD" (2x16 text read-out thingy)
appears to be doing a similar thing too[3].

Does the access method in question ring a bell as being close to any of the
other drivers?

	-Paul

[0] http://thread.gmane.org/gmane.linux.usb.general/15802
[1] http://launchpad.net/igotu2gpx/+download
[2] http://lwn.net/Articles/82642/
[3] http://codeka.com/forums/viewtopic.php?f=3&t=23&st=0&sk=t&sd=a#p148
[4] http://www.paul.sladen.org/toys/igotu/test.py
-- 
Why do one side of a triangle when you can do all three.  Somewhere, GB.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/