MeeGo has a new version of iphb that allows a different kind of interval to be passed to iphb_wait(). Currently we pass the minimum and maximum number of seconds we want to be waken up from now. With iphb 0.61.29 we can pass the same interval both as minimum and maximum value and that means we want to be waken up every x seconds (so the first time it could be much shorter). If we use this feature with a set of recommended intervals (used also by other applications) we can get a better power usage as all the application will be waken up at the same time.
http://cgit.collabora.co.uk/git/user/bari/wocky.git/log/ contains the patch to fix this. Note that iphb didn't bump their API version number when adding those defines, so we cannot ad a configure check. I complained about it and hopefully it will be fixed soon, but if you could review this in the meantime it could be useful :)
Looks good to me.
You might be able to configure-check it via: AC_CHECK_DECL([IPHB_GS_WAIT_30_MIN], [$LIBIPHB_CFLAGS]) or some such?
(In reply to comment #3) > AC_CHECK_DECL([IPHB_GS_WAIT_30_MIN], [$LIBIPHB_CFLAGS]) er, AC_CHECK_DECL([IPHB_GS_WAIT_30_MIN], [have_new_iphb=yes], [have_new_iphb=no], [$LIBIPHB_CFLAGS])
(In reply to comment #4) > (In reply to comment #3) > > AC_CHECK_DECL([IPHB_GS_WAIT_30_MIN], [$LIBIPHB_CFLAGS]) > > er, AC_CHECK_DECL([IPHB_GS_WAIT_30_MIN], [have_new_iphb=yes], > [have_new_iphb=no], [$LIBIPHB_CFLAGS]) They will fix the .pc file. But it seems they want to change their defines now, so this will have to wait...
Can you please take a look again? I added a “configure: depend on libiphb >= 0.61.31” patch and modified “Heartbeat: synchronise the wakeups with other applications” with the updated intervals.
Pushed to master.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.