On Sat, Jul 16, 2005 at 12:39:03AM +0200, Bernd Eckenfels wrote:
In article [EMAIL PROTECTED] you wrote:
Sorry. The main idea is making power management more effective, that's
why earlier is better here.
I dont see why this is the case. in the bootup phase the system is loaded
anyway, no
On Mon, Jul 18, 2005 at 09:35:26PM +0200, Bernd Eckenfels wrote:
In article [EMAIL PROTECTED] you wrote:
You don't know that actually.
There are far too many usages to make a generic statement like that.
I can't see nothing wrong or useless in trying to maximize battery
power and/or
In article [EMAIL PROTECTED] you wrote:
You don't know that actually.
There are far too many usages to make a generic statement like that.
I can't see nothing wrong or useless in trying to maximize battery
power and/or minimize heat generation.
Yes of course, however there is a big difference
* Mattia Dongili
| On Sat, Jul 16, 2005 at 12:39:03AM +0200, Bernd Eckenfels wrote:
| In article [EMAIL PROTECTED] you wrote:
| Sorry. The main idea is making power management more effective, that's
| why earlier is better here.
|
| I dont see why this is the case. in the bootup phase
Hi,
* Andrew Suffield [EMAIL PROTECTED] [2005-07-15 10:50]:
On Thu, Jul 14, 2005 at 11:21:52AM +0200, Tollef Fog Heen wrote:
* Mattia Dongili
| - setting the CPUFreq policy must be done as early as possible in the
| boot process (IMHO)
Why? This looks just like an opinion
On Thu, Jul 14, 2005 at 11:21:52AM +0200, Tollef Fog Heen wrote:
* Mattia Dongili
| - setting the CPUFreq policy must be done as early as possible in the
| boot process (IMHO)
Why? This looks just like an opinion without any rationale.
Sorry. The main idea is making power management
On Fri, Jul 15, 2005 at 10:52:52AM +0200, Nico Golde wrote:
Hi,
* Andrew Suffield [EMAIL PROTECTED] [2005-07-15 10:50]:
On Thu, Jul 14, 2005 at 11:21:52AM +0200, Tollef Fog Heen wrote:
* Mattia Dongili
| - setting the CPUFreq policy must be done as early as possible in the
|
In article [EMAIL PROTECTED] you wrote:
Sorry. The main idea is making power management more effective, that's
why earlier is better here.
I dont see why this is the case. in the bootup phase the system is loaded
anyway, no need to throttle it. especially since this one minute does not
consume
* Mattia Dongili
| - setting the CPUFreq policy must be done as early as possible in the
| boot process (IMHO)
Why? This looks just like an opinion without any rationale.
--
Tollef Fog Heen,''`.
UNIX is user friendly, it's just picky
On Thu, Jul 14, 2005 at 11:21:52AM +0200, Tollef Fog Heen wrote:
* Mattia Dongili
| - setting the CPUFreq policy must be done as early as possible in the
| boot process (IMHO)
Why? This looks just like an opinion without any rationale.
It's dumb anyway. If you wanted it set early,
Hello *,
in closing #311604 I'm adding an init script to the package along with
its /etc/default entry to set a default governor on boot.
Anyway while reasoning on the script start order number I realized that
it might be good to have it into rcS.d instead of the default choice.
cpufreq-set only
11 matches
Mail list logo
