On Mon, 2010-08-30 at 11:48 -0700, Kevron Rees wrote: > 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.
Unfortunately, almost everything about AGPS is proprietary. Although there are a handful of standards such as SUPL, most of the interfaces are proprietary (to the GPS, from the network operator, from the modem, etc). Although it would be possible to create an open source SUPL client, doing so is no trivial task. There are certification requirements, not to mention that having a client is only half of the solution. Commercial stacks may appear that have AGPS support enabled for their hardware. This should made be available tying into a backend of the Qt-Mobility Location API. There is no MeeGo API for getting assistance data to the application. Application writers should expect to use the Qt-Mobility Location API for getting position. Cheers > > > > > On Mon, Aug 30, 2010 at 10:26 PM, Kevron Rees > > <kevron_m_r...@linux.intel.com > >> 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. > >> > >> _______________________________________________ > >> MeeGo-dev mailing list > >> MeeGo-dev@meego.com > >> http://lists.meego.com/listinfo/meego-dev > >> > > > > _______________________________________________ > MeeGo-dev mailing list > MeeGo-dev@meego.com > http://lists.meego.com/listinfo/meego-dev -- Michael Leibowitz <michael.leibow...@intel.com> _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
