implementation status of the Gypsy interface

[Daniel Willmann]

Just an update on the current Gypsy interface status:

On Tue, 9 Sep 2008 01:07:45 +0200
Daniel Willmann <daniel at totalueberwachung.de> wrote:

> Hi,
> 
> On Mon, 8 Sep 2008 21:46:58 +0200
> Sascha Wessel <wessel at nefkom.net> wrote:
> 
> > There is also the org.freesmartphone.GPS interface with a SetPower
> > method. Maybe we can remove this and instead implement the Gypsy
> > methods Start and Stop for the org.freedesktop.Gypsy.Device
> > interface? Or even better, use the org.freesmartphone.Usage
> > interface for power control?
> 
> Yeah, I know that's not really nice at this point. The root problem is
> deciding what subsystem is responsible for starting/stopping the GPS.
> Since we have ousaged with policies off/on/auto it needs to retain a
> certain control over power which wouldn't be the case if it was
> integrated with Start and Stop.

This is basically finished now. Start/Stop track the user through name
owner changed signals and call RequestResource on first Start and
ReleaseResource once the last user vanished.
So Gypsy applications should run just fine without any awareness of the
framework.

> > Hmm, or do I miss sth? The gypsy integration is a bit confusing.
> > Ok, trying to summarize the current ogpsd dbus interface...

> > connection (bus name):
[...]

> > interface (interface name):
> > * org.freesmartphone.GPS
> >   - method: SetPower			(problematic for more
> > than one client, remove?)

This ugly thing is gone since power control has undergone a major
overhaul.

> > * org.freedesktop.Gypsy.Server
> >   - method: Create                      (stub only)
> >   - method: Shutdown                    (stub only)
> 
> We'd need to implement that if we want to be able to use different GPS
> on the fly, this isn't that important at the moment IMHO.

This is still only a stub.

> > * org.freedesktop.Gypsy.Device
> >   - method: Start                       (stub only)
> >   - method: Stop                        (stub only)
> 
> Is basically what ousaged does.

Yes, but gypsy applications only know about this, they are now
relaying the requests to ousaged.

> >   - method: GetConnectionStatus 	(patch available)
> >   - method: GetFixStatus 		(ok)
> >   - signal: ConnectionStatusChanged 	(patch available)
> 
> Thanks for the patches, please give me some time after MS3 and I'll go
> through them. This week I wont really get much work done anyways, but
> starting next week (if PDU mode doesn't fail miserably :-) I'll have
> some time to work on GPS again.

This is working now

> > * org.freedesktop.Gypsy.Time
> >   - mehtod: GetTime 			(ok)
> >   - signal: TimeChanged 		(ok)
> 
> I'm actually not sure that frameworkd produces the same time that
> gypsy does...
This is still the case, I guess I need to dig into the Gypsy code
again. :-)


> Regards,
> Daniel Willmann
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.linuxtogo.org/pipermail/smartphones-standards/attachments/20080930/cd139cce/attachment-0001.pgp>