Nevermind, filed a bug (there is also a workaround if you run into this issue): https://bugs.freedesktop.org/show_bug.cgi?id=31173
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext [email protected] Sent: Wednesday, October 27, 2010 11:04 AM To: [email protected] Subject: [MeeGo-dev] meego geoclue gypsy Hi, has somebody found a good way to have (GeoClueMaster/GeoClueProvider-) Gypsy working with MeeGo? E.g. somehow on N900 image, or chroot'd SDK, or image on QEMU? Any tips on what has worked are appreciated. Alternatively if you can see what I'm doing wrong here, any tips much appreciated: So far I've tried external USB GPS dongle on my 9.10 Ubuntu running chroot'd Netbook SDK image from July-10. The GPS device (BU-353) does get a fix and I can e.g. 'cat' the NMEA ASCII on terminal. I've set the baud rate of the device to 4800. However when (manually, autostart does not work for some reason) starting the Gypsy daemon and then running the simple geoclue gypsy example from http://folks.o-hand.com/jku/geoclue-docs/simple-example.html (changing the device name though): ** (gypsy-daemon:5676): DEBUG: Creating client for /dev/ttyUSB0 ** (gypsy-daemon:5676): DEBUG: Device name: ttyUSB0 ** (gypsy-daemon:5676): DEBUG: Registered client on /org/freedesktop/Gypsy/ttyUSB0 ** (gypsy-daemon:5676): DEBUG: Starting connection to /dev/ttyUSB0 ** (gypsy-daemon:5676): DEBUG: GPS channel can connect ** (gypsy-daemon:5676): WARNING **: GARMIN: "Private Info Resp" packet data not recognized ** (gypsy-daemon:5676): WARNING **: Error determining device type for /dev/ttyUSB0 And the example program itself remains waiting for position changes (no errors occur). Cheers, Juha _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
