fso bug/oddity

Am Wednesday 17 September 2008 17:54:54 schrieb Tilman Baumann:
> Michael 'Mickey' Lauer wrote:
> > Am Wednesday 17 September 2008 16:16:43 schrieb Tilman Baumann:
> >> Tilman Baumann wrote:
> >>> dbus is getting flodded by org.freedesktop.Gypsy.Time.TimeChanged,
> >>> org.freedesktop.Gypsy.Satellite.SatellitesChanged and
> >>> org.freedesktop.Gypsy.Time.TimeChanged signals.
> >>> But GPS is off.
> >>>
> >>> I think neither of the events makes sense in this case and wastes
> >>> cycles. Probably not good for battery life.
> >>
> >> I just had a look at the fso apis again. And i almost fell of my chair.
> >> I just found org.freesmartphone.Device.RealtimeClock
> >> What is wrong with gettimeofday anc co with all it's beauty?
> >
> > Last time I checked gettimeofday reads from system time.
> > org.freesmartphone.Device.RealtimeClock is a dbus interface to program
> > the RealtimeClock (sic!).
>> My mistake. But what about /dev/rtc and the hwclock command?
programming /dev/rtc works fine from C and asm, much less so for higher level
languages. I felt a dbus interface for that would be nice. It's not in use
yet, but we need something like that anyways when we want to support waking
up arbitrary dbus clients for PIM events.
--
:M: