On Fri, 26 Aug 2005 13:16:31 +0200, Stefan Seyfried wrote: > Anton Farygin wrote: >> Great ! >> >> Danny, where possible download current unstable version ? only from CVS >> ? > > yes, only from CVS now. We should do a release, now that the biggest > changes are done, but our schedule is pretty tight right now :-( > > Until then, use: > - powersave CVS HEAD > - kpowersave CVS DBUS_INTEGRATION branch (this is actually where the > DBUS work took place and it will be merged back into HEAD, but right > now it is the latest and greatest). > >> I plan build it for ALT Linux Sisyphus (unstable ALT Linux repository) >> after hal-0.5.4 release. (for testing) > > cool. > Powersave HEAD may have rough edges building, but if it builds, it should > run just fine :-) > > We now use HAL to acquire battery info. The communication with the clients > (kpowersave etc) is done via DBUS now, we got rid of the socket interface.
It's great. Previos stable kpowersave lost connetion to powersave (0.9.25) socket from time to time (reproduced on livecd when notebook run on battery). I don't know how to find this issue. And it not higher-priority problem for me. > We also made acpid mandatory for both powersave and hal to dispatch the > ACPI events, so the problem of many processes competing for > /proc/acpi/event is mostly solved (powersaved can still access > /proc/acpi/event, but it does not fallback from acpid to /proc, it just > waits for acpid to reappear). Danny can tell you more about the hal stuff > (hal also has to wait for acpid to reappear and not grab > /proc/acpi/event), but IIUC most of those patches are submitted back > upstream. I see it later, on next week... my schedule overloaded too ;-( Rgds, Anton Farygin ALT Linux Team _______________________________________________ powersave-devel mailing list [email protected] http://forge.novell.com/mailman/listinfo/powersave-devel
