----- "Nasa" <[email protected]> wrote: > > > > Hi, > > > > > > > > Geoclue master provider uses gconf key to set the gps device > for > > > Gypsy. > > > > Below is one of the example which sets the path to bluetooth > > > device. > > > > > > > > gconftool-2 -t string -s > > > > /apps/geoclue/master/org.freedesktop.Geoclue.GPSDevice > > > 00:02:76:C5:81:BF > > > > > > > > AFAIK, gypsy has support for Serial gps devices and Bluetooth > > gps. > > > Hence, > > > > I > > > > was wondering how gypsy will be talking to AGPS, SUPL for > > different > > > set of > > > > Meego devices ? > > > > > > > > Cheers , > > > > Sanny > > > > > > > > > > AFAIK, there is no supl support in gypsy at the moment. The > > problem > > > is, > > > there seems to be no standard way to feed agps data back to the > gps > > > device. Device mfg's use proprietary command sets to achieve > this. > > > > > Getting the agps data from supl is probably the easy part. > Finding > > a > > > generic way to feed that data to the gps device is a bit harder. > > > > > > > > > > > On Mon, Aug 30, 2010 at 10:26 PM, Kevron Rees > > > > <[email protected] > > > >> wrote: > > > > > > > >> [snip] > > > >> >> Hi nasa, > > > >> >> > > > >> >> gypsy requires some application to have knowledge of the > > device > > > and > > > >> to > > > >> >> set > > > >> >> it up via the gypsy dbus api. I was told that gypsy should > > > really be > > > >> >> used > > > >> >> with some sort of management layer like geoclue which I > > assume > > > has > > > >> >> some > > > >> >> sort of configuration that it reads. > > > >> >> > > > >> >> In IVI, this management layer should start automatically > when > > > an > > > >> >> application requests a gps fix (via the dbus launching > > > mechanism). I > > > >> >> don't know if this is the case however. > > > >> >> > > > >> >> Hope that helps. As I understand, the qt-mobility location > > > backend > > > >> >> for > > > >> >> meego will be geoclue/gypsy. So that should at least > > abstract > > > >> >> application > > > >> >> writers from having to know the details of the device. > > > >> >> > > > >> >> cheers, > > > >> >> -Kevron > > > >> > > > > >> > Thanks Kevron, > > > >> > > > > >> > so I get gypsy/geoclue and I noted that navit can/does use > > gypsy > > > (not > > > >> sure > > > >> > about geoclue). It seems unclear to me (and I guess you as > > well) > > > how > > > >> to > > > >> > configure gpysy to use an actual gps device. Looking on > > gypsy's > > > >> website > > > >> > ( http://gypsy.freedesktop.org/wiki/ ) doesn't help with > > figuring > > > that > > > >> > out. > > > >> > And, of course, geoclue is another layer above gypsy. > > > >> > > > > >> > I also thought I read somewhere that geoclue works with > gpsd... > > > > > Is > > > >> that > > > >> > correct? > > > >> > > > > >> > > > >> geoclue can work with either gpsd or gypsy. If you have > geoclue > > > >> running, > > > >> and configured correctly, it should set up gypsy with the > right > > > device > > > >> (i > > > >> think). After that it's just a matter of getting navit to use > > it. > > > >> > > > > Ok, > > > > So I've been trying for the last day to configure navit.xml.local > to > > get the data from gypsy (or should it be geoclue?) without much > love. > > Does anyone know how to get this to work? > > > > For additional points -- this there a way to check gps data from > > geoclue > > without navit?
Just to keep this thread alive.... Is this a use case that is being worked for meego (ie: usb attached gps reciever that provides gps data to navit for general naviation features)? Nasa _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
