Power Management Software: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Clean up page)
 
(3 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{dated}}{{cleanup}}
== Design ==
== Design ==


* [[Power Management Interface]]
* [[Power Management Interface]]
* [[Power Management Scenarios]]


== Open bugs ==
== Open bugs ==


* Suspend and resume not working yet: http://dev.laptop.org/ticket/508
* {{Trac|508|Suspend and resume not working yet}}
* The battery charging algorithms have problems
* The battery charging algorithms have problems


Line 31: Line 33:
* Software control of backlight in HAL.
* Software control of backlight in HAL.
* Small session daemon created that exposes a similar DBUS interface to g-p-m.
* Small session daemon created that exposes a similar DBUS interface to g-p-m.
* Sugar UI element created for telling how much charge we have left
* Sugar UI element created for telling how much charge we have left (DONE)
* Sugar UI emement created for configuration?
* Sugar UI element created for configuration?


[[Category:Hardware]]
[[Category:Hardware]]
[[Category:Software development]]
[[Category:Software development]]
[[Category:Battery & Power]]

Latest revision as of 08:08, 6 February 2008

Emblem-warning.png The currency of this article or section may be limited by out-of-date information.
There may be relevant discussion on its talk page


Design

Open bugs

Frequently Asked questions

  • Why does the power button (hardware) do nothing? Will it send out keycodes or some other events in the future?
  • It does send a keycode
  • How do you change the backlight brightness from a program (rather than the keyboard buttons)?
  • How is the brightness level being changed? Some embedded EC? OF? Do we get a userspace signal/event when the user changes it?
  • DPMS seems not to work. "sleep 1 && xset dpms force off" does nothing.
  • DPMS needs to be taught how to work with the DCON
  • Where are per-session settings meant to be stored? GConf? How much configuration should there be allowed?
  • What?

Current Priorities:

  • Stable Suspend to RAM (Stable means: pass 1000 consecutive suspend/resume cycles without a glitch)
  • Battery class stuff integrated with HAL.
  • Software control of backlight in HAL.
  • Small session daemon created that exposes a similar DBUS interface to g-p-m.
  • Sugar UI element created for telling how much charge we have left (DONE)
  • Sugar UI element created for configuration?