Sebastian Spaeth <[email protected]> writes: > Can that be a problem for fflarms doesn't wake up issue? : > rtcwake -d /dev/rtc -s 20 > rtcwake: can't open '/dev/rtc0': Device or resource busy > > If "cat /dev/rtc" fails with "resource busy" then > atd-over-fso will fail here for sure too: > rtcfd = open ("/dev/rtc", O_RDONLY); > > fuser /dev/rtc0 > 1345 -----> /usr/bin/fsodeviced > > fsodeviced exclusively hogs /dev/rtc which makes atd fail.... > > GUILTY AS CHARGED. I HEREWITH BAN FSODEVICED FROM HOGGING UP MY DEVICES > WITH IMMEDIATE EFFECT. :) > > (atd-over-fso code is here) > http://handhelds.org/cgi-bin/cvsweb.cgi/apps/atd/atd.c?rev=1.6&content-type=text/x-cvsweb-markup&only_with_tag=HEAD
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). When I was looking at the issue in March 2009 it seemed not to be doing that, so I made atd-over-fso ensures that (i.e. did not removed the code inherited from atd which sets rtc from system time before setting alarm). (I have not look into this issue since that time). _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
