[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: [PATCH] powerdevil-remove-cpufreq.patch
From:       Sebastian Wiesner <basti.wiesner () gmx ! net>
Date:       2010-03-08 15:06:19
Message-ID: 201003081606.26888.basti.wiesner () gmx ! net
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Sunday 07 March 2010 23:57:37 Holger Macht wrote
> Remove all CPU frequency scaling code from powerdevil and the kcm
> module. You should never offer those options to the user because he
> might not understand what the impact is. You only want a dynamic
> frequency algorithm which is the default these days (ondemand
> governor). A good explanation is provided in [1].

I do not object the point, but saving power is really not all I care for.   At 
least for my part, controlling and limiting  head and noise emission is often 
much more important than lengthening battery lifetime as much as possible.  In 
many situations, I prefer a system, that is cool and silent even under heavy 
load.  Therefore I do not only have a "power plug" and "battery" profile, but 
also a "silent" and a "movie" profile, both using the powersave governor to 
limit CPU frequency and hence head, fan speed and noise.

Of course, if these options are removed, I can still use other tools to limit 
CPU frequency, but none of them is as convenient as powerdevil with its 
integration into KDE.  Therefore, I'd really miss these options, if the were 
removed from powerdevil.

Complete removal is really "harsh".  A GUI, that makes clear, that the 
ondemand governor is preferable and absolutely recommended, but still lets the 
user choose a different governor, if she wants, is a much friendlier approach, 
IMHO.

-- 
Freedom is always the freedom of dissenters.
                                      (Rosa Luxemburg)

["signature.asc" (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]