On Mon, Oct 04, 2010 at 03:07:39PM +0200, Joachim Ott wrote:
> On 4 October 2010 13:50, Timo Juhani Lindfors <timo.lindf...@iki.fi> wrote:
> > Joachim Ott <jo.o...@googlemail.com> writes:
> >> SHR uses fso-gpsd. There is no need to use hexdump for /dev/gps, it's
> >
> > Afaik fso-gpsd does not read from /dev/gps but instead relies on some
> > lower level daemon to actually fetch the data?
>
> fso-gpsd connects to ogpsd via dbus, the devicename (dev/ttySAC1) is
> specified in /etc/frameworkd.conf.
Yes, from my original post, I'm running debian;
# cat /proc/version
Linux version 2.6.29-20100313.git973a41fc (r...@neo) (gcc version 4.4.5
20100728 (prerelease) (Debian 4.4.4-8) ) 1 Sat Aug 7 17:45:57 GMT-3 2010
with frameworkd running ogpsd. The frameworkd log shows a position (which
I've obscurred):
2010.10.01 01:39:08.43 ogpsd DEBUG Got UBX packet of type
NAV-POSLLH: [{'LON': -123xxxxxxx, 'HMSL': 28843, 'HEIGHT': 11546, 'ITOW':
463141000, 'LAT': 48xxxxxxx, 'Vacc': 999998976, 'Hacc': 999998976}]
Is this position just the persistent data, or is ogpsd actually getting this
from the gps chip?
I find it odd, that the frameworkd/ogpds logs show a position, but if I
query the position from the dbus interface, I get nothing. For example:
# mdbus -s org.freedesktop.Gypsy /org/freedesktop/Gypsy
org.freedesktop.Gypsy.Position.GetPosition
(0, 0, 0.0, 0.0, 0.0)
> fso-gpsd connects to ogpsd via dbus, the devicename (dev/ttySAC1) is
> specified in /etc/frameworkd.conf.
Last time I did a pacakge update (Friday), debian _removed_ fso-gpsd. Does
anyone know why? It seems to be mutually exclusive with tangogps/foxtrotgps
in the package dependencies, which I don't understand, because as far as I
know they rely on fso-gpsd (i.e. they aren't written for the dbus interface
yet).
~James
_______________________________________________
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
