Ticket #448 (assigned defect)

Opened 6 years ago

Last modified 5 years ago

We need an alarm daemon

Reported by: alphaone@… Owned by: openmoko-devel
Priority: high Milestone:
Component: unknown Version: current svn head
Severity: normal Keywords:
Cc: buglog@… Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: no PatchReviewResult:
Reproducible:

Description

See ​http://wiki.openmoko.org/wiki/Alarm_daemon for implementation details

Change History

comment:1 Changed 5 years ago by wolfgang@…

  • Owner changed from buglog@… to michael@…

comment:2 Changed 5 years ago by andy

The Wiki thing is outdated, the howto is a 404 and the project pointed to from Maemo has "never released any files" since 2006.

I agree we need some kind of scheduler that can burn through suspend and manage a queue of forward requests though -- but maybe this should be in kernelspace.

comment:3 Changed 5 years ago by roh

  • Owner changed from michael@… to michael

comment:4 Changed 5 years ago by john_lee

  • Status changed from new to assigned
  • Owner changed from michael to openmoko-kernel
  • HasPatchForReview unset
  • Component changed from alarm handling to System Software

last update is 4 months ago. should this be done in kernelspace ?

comment:5 Changed 5 years ago by john_lee

  • Owner changed from openmoko-kernel to openmoko-devel
  • Component changed from System Software to unknown

should be fixed in ompower.

Note: See TracTickets for help on using tickets.