RealTimeClock

[Joerg Reisenweber]

Am Do  19. März 2009 schrieb Michael 'Mickey' Lauer:
> On Thursday 19 March 2009 14:39:19 Sven Klomp wrote:
> > On Thursday 19 March 2009 14:05:05 Michael 'Mickey' Lauer wrote:
> > > I wonder why it takes a string as opposed to a double.
> > >
> > > If you think double is more appropriate, feel free to open a bug report
> > > (trac.fso)
> >
> > Done.
> >
> > Maybe it is the wrong mailinglist.
> 
> smartphones-standards at linuxtogo.org would fit most.
> 
> > However, I wonder if an API for the RTC
> > is planed that takes care of multiple wake up times? Until now, I have to
> > take care if another application set the time already...
> 
> RTC is probably going to stay like that, since it's a low level interface. 
The 
> big picture is that the (higher level) PIM service would handle this, e.g. 
> once it knows about all your appointments, it can always compute the next 
> alarm that is due and program the RTC accordingly.

Nope, has to be done by some middleware. There might be RTC-alarms from other 
sources than just PIM. (e.g. GPS, bat management etc pp)
I suggest patching cron & at, as it seems the most natural interface for 
RTC-alarm.
/j
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.openmoko.org/pipermail/devel/attachments/20090324/609a7690/attachment.pgp