Power Management Software: Difference between revisions
Jump to navigation
Jump to search
(create some quick notes for me) |
m (categorization) |
||
| Line 24: | Line 24: | ||
* Sugar UI element created for telling how much charge we have left |
* Sugar UI element created for telling how much charge we have left |
||
* Sugar UI emement created for configuration? |
* Sugar UI emement created for configuration? |
||
[[Category:Hardware]] |
|||
[[Category:Software development]] |
|||
Revision as of 03:26, 6 January 2007
Clever Power Management
Open bugs:
- Suspend and resume not working yet: http://dev.laptop.org/ticket/508
- The battery charging algorithms have problems
Other questions:
- Why does the power button (hardware) do nothing? Will it send out
keycodes or some other events in the future?
- 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.
- Where are per-session settings meant to be stored? GConf? How much configuration should there be allowed?
Current Priorities:
- 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
- Sugar UI emement created for configuration?