On Thu, Mar 12, 2009 at 05:53:01PM +0100, paul van den berg wrote: > Greg KH <greg@xxxxxxxxx> wrote: > > > Try the navman driver instead. You can either add the device id to the > > driver and rebuild it, or do this before you plug the device in: > > modprobe navman > > echo -n "0x0df7 0x0900" > /sys/bus/usb-serial/drivers/navman/new_id > > > > and then plug your device in and see if that works. > > > > Let me know how it goes. > > > It works!: Great!. I'll add a new device id entry to this driver. Or if you want to, could you send me a patch as described in Documentation/SubmittingPatches adding it so you get the authorship credit? > dmesg: > usb 1-10: new full speed USB device using ohci_hcd and address 3 > usb 1-10: configuration #1 chosen from 1 choice > navman 1-10:1.0: navman converter detected > usb 1-10: navman converter now attached to ttyUSB0 > usb 1-10: New USB device found, idVendor=0df7, idProduct=0900 > usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > usb 1-10: Product: GT100/GT200 > usb 1-10: Manufacturer: Mobile Action > > # gpsd -b -N -D2 /dev/ttyUSB0 > gpsd: launching (Version 2.37) > gpsd: listening on port gpsd > gpsd: successfully connected to the DBUS system bus > gpsd: running with effective group ID 0 > gpsd: running with effective user ID 0 > gpsd: opening read-only GPS data source at '/dev/ttyUSB0' > gpsd: speed 9600, 8N1 > gpsd: garmin_gps not active. > gpsd: gpsd_activate(0): opened GPS (5) > gpsd: ntpd_link_activate: 0 > gpsd: closing GPS=/dev/ttyUSB0 (5) > > and after starting xgps: > gpsd: client 127.0.0.1 (0) connect on fd 5 > gpsd: opening read-only GPS data source at '/dev/ttyUSB0' > gpsd: speed 9600, 8N1 > gpsd: garmin_gps not active. > gpsd: gpsd_activate(1): opened GPS (6) > > gpsd gave some messages, but xgps worked! > gpsd: => GPS: $PSRF100,0,9600,8,1,0*0C\x0d\x0a FAILED > gpsd: => GPS: $PGRMCE*0E\x0d\x0a FAILED > gpsd: => GPS: $PFEC,GPint*58\x0d\x0a FAILED > gpsd: => GPS: $PFST*11\x0d\x0a FAILED > gpsd: => GPS: $PFEC,GPsrq*5B\x0d\x0a FAILED > gpsd: LOS matrix is singular, can't calculate DOPs. > gpsd: => GPS: $PASHQ,RID*28\x0d\x0a FAILED > gpsd: LOS matrix is singular, can't calculate DOPs. > gpsd: LOS matrix is singular, can't calculate DOPs. > gpsd: LOS matrix is singular, can't calculate DOPs. > gpsd: unknown sentence: "$PSRFTXT,GSW3.2.5_3.3.01.06-ADS-SDK001P1.00*16\x0d\x0a" > gpsd: unknown sentence: "$PSRFTXT,MO-20080226-SSB57600_S_DM1-LX*49\x0d\x0a" > [...] > > So this is good enough to use the device as gps receiver, but it also > is a data logger, so I need some way to download recorded tracks and > waypoints from the device. > There are more functions: clear recorded tracks, set tracklog speed, .. > Any hints? I have no idea, the driver has nothing to do with that, it just gets data from the device. I suppose there might be a way to send commands back to it, but that would have to go through the control channel. Hm, I wonder if we just make the write section to go through that... Can you try kernel patches? I'll be glad to make something up to try this out if you want to. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
