On Fri 08. Dec - 14:54:49, Stefan Seyfried wrote:
> Hi Holger,
>
> first: thanks for updating the documentation, this is really needed :-)
I had just a quick look to fix the most important issues.
>
> On Thu, Dec 07, 2006 at 04:38:30PM -0700, Novell Forge SVN wrote:
>
> > -The powersave daemon defines three battery states:
> > +The powersave daemon defines three battery states. They will only be taken
> > +into account if no other application caring about power management (such
> > +as kpowersave or gnome-power-manager) is running.
>
> > Modified: trunk/powersave/docs/README.buttons
> > ===================================================================
> > --- trunk/powersave/docs/README.buttons 2006-12-06 04:00:49 UTC (rev
> > 2733)
> > +++ trunk/powersave/docs/README.buttons 2006-12-07 23:38:22 UTC (rev
> > 2734)
> > @@ -1,3 +1,7 @@
> > +These settings will only be taken into account if no other application
> > +caring about power management (such as kpowersave or gnome-power-manager)
> > +is running.
>
> > Modified: trunk/powersave/docs/README.cpufreq
> > ===================================================================
> > --- trunk/powersave/docs/README.cpufreq 2006-12-06 04:00:49 UTC (rev
> > 2733)
> > +++ trunk/powersave/docs/README.cpufreq 2006-12-07 23:38:22 UTC (rev
> > 2734)
> > @@ -1,3 +1,7 @@
> > +The Powersave Daemon will only care about CPU frequency scaling if no
> > +other application caring about power management (such as kpowersave or
> > +gnome-power-manager) is running.
>
> > Modified: trunk/powersave/docs/README.internals
> > ===================================================================
> > --- trunk/powersave/docs/README.internals 2006-12-06 04:00:49 UTC (rev
> > 2733)
> > +++ trunk/powersave/docs/README.internals 2006-12-07 23:38:22 UTC (rev
> > 2734)
> > @@ -1,9 +1,9 @@
> > @section The Daemon
> >
> > - The heart of the package is the daemon (@code{/usr/sbin/powersaved}).
> > - It listens for client requests (normally from non-root users), listens
> > - for hardware changes and checks e.g. the CPU load to adjust the CPU
> > - frequency dynamically.
> > + The heart of the package is the daemon
> > + (@code{/usr/sbin/powersaved}). It listens for hardware changes
> > + and checks e.g. the CPU load to adjust the CPU frequency
> > + dynamically.
>
> Does it still do that?
No ;-)
>
> > Modified: trunk/powersave/docs/README.schemes
> > ===================================================================
> > --- trunk/powersave/docs/README.schemes 2006-12-06 04:00:49 UTC (rev
> > 2733)
> > +++ trunk/powersave/docs/README.schemes 2006-12-07 23:38:22 UTC (rev
> > 2734)
> > @@ -1,3 +1,7 @@
> > + These settings will only be taken into account if no other application
> > + caring about power management (such as kpowersave or
> > gnome-power-manager)
> > + is running.
>
> Generally this is not true. An application can care about it, but if it
> doesn't grab the DBus interface, it won't matter, or am i wrong?
In the end every application caring about this will grab this
interface. Otherwise it would be a bug. I intended to send a request to
the freedesktop list defining a standard for this already some time ago
but didn't find the time. I already had some discussions with David
Zeuthen about this and we generally agree. The missing piece is just that
someone has to write this down ;-)
> So explaining somewhere what exactly (in technical terms) an application has
> to do to count it as "caring about power management" would be good.
Either this, or maybe a reference somewhere to freedesktop if this will be
accepted. But we are not there yet.
>
> Thanks :-)
>
> Stefan
Regards,
Holger
_______________________________________________
powersave-devel mailing list
[email protected]
http://forge.novell.com/mailman/listinfo/powersave-devel
