Ticket #492 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

fsodeviced hogs /dev/rtc exclusively

Reported by: spaetz Owned by: mickey
Priority: major Milestone:
Component: cornucopia/fsodevice Version:
Keywords: Cc:

Description

1) Run current /dev/fsodeviced 2) cat /dev/rtc Device or resource busy: '/dev/rtc'

3) FAIL. This is what makes atd-over-fso fail as it tries to open /dev/rtc read-only. Manifests itself in that device doesn't wake up when ffalarms are supposed to occur (they occur when you manually resume though).

Thanks for fixing :-)

Change History

comment:1 Changed 2 years ago by spaetz

  • Version milestone5.5 deleted
  • Component changed from framework/general to cornucopia/fsodevice

comment:2 Changed 2 years ago by mickey

fsodeviced needs to hold /dev/rtc to get wakeup IRQs when the system is not sleeping. fsodeviced's implementation of org.freesmartphone.Device.RealtimeClock? is meant to abstract the RTC's interface -- what is atd-over-fso actually doing? Can you implement the functionality that needs direct access to the RTC via the DBus API?

comment:3 Changed 2 years ago by mickey

  • Status changed from new to closed
  • Resolution set to fixed

Author: Michael 'Mickey' Lauer <mickey@…> Date: Tue Nov 24 02:10:33 2009 +0100

fsodeviced: kernel26_rtc: be more cooperative with /dev/rtc0

This module will now only hold /dev/rtc0 while it is a) doing any operation (which is very short), or b) waiting for a pending alarm (in which case we do not want someone else to remove or change it behind our back anyways).

This should improve FSO #492 to a certain extent.

Please open another bug, if you are missing something in the RTC DBus API.

Note: See TracTickets for help on using tickets.