On Mon, Nov 23, 2009 at 14:54, Sebastian Spaeth <sebast...@sspaeth.de> wrote: > Łukasz Pankowski wrote: >> The question here is whether otimed (or fsodeviced or whatever) ensures >> /dev/rtc matches system clock when >> org.freesmartphone.Time.Alarm.SetAlarm is called (or somewhere else). > > otimed is responsible for setting the system clock. And that has no > access as long as fsodeviced locks access. (BTW, I verified that I can > "cat /dev/rtc0" after killing fsodeviced). > > Just try a simple > hwclock -f /dev/rtc0
otimed uses odeviced interface to set system clock, so that shouldn't be a problem. -- Sebastian Krzyszkowiak dos _______________________________________________ Shr-devel mailing list Shr-devel@lists.shr-project.org http://lists.shr-project.org/mailman/listinfo/shr-devel
