From: Felix Braun <Felix.Braun@mail.mcgill.ca>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: CPUFreq@lists.linux.org.uk,
Dominik Brodowski <linux@dominikbrodowski.net>,
davej@redhat.com
Subject: Re: [PATCH 2.6.14] cpufreq: don't suggest speedstep-centrino for Dothan-based Celeron-M processors
Date: Fri, 2 Dec 2005 15:52:35 +0100 [thread overview]
Message-ID: <20051202155235.1e83e932@tilion.getrex.org> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB60067F3B26@scsmsx403.amr.corp.intel.com>
On Fri, 02 Dec 2005 06:26:52 -0800 "Pallipadi, Venkatesh"
<venkatesh.pallipadi@intel.com> wrote:
> P4-clockmod will only do the duty-cycle based throttling and will
> not save any significant power. In fact, CPU may end up consuming more
> power than without it [...]. It will only help in thermal conditions
> and ACPI throttling driver should handle that anyway.
By "ACPI throttling driver" do you mean arch/i386/.../acpi_cpufreq? That
driver didn't work for me :-( I get a error: no such device when I try to
load it as a module. I haven't looked into that yet.
Anyway, thanks a lot for the information
Felix
next prev parent reply other threads:[~2005-12-02 14:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 14:26 [PATCH 2.6.14] cpufreq: don't suggest speedstep-centrino for Dothan-based Celeron-M processors Pallipadi, Venkatesh
2005-12-02 14:52 ` Felix Braun [this message]
2005-12-02 15:04 ` Bruno Ducrot
-- strict thread matches above, loose matches on Subject: below --
2005-12-02 21:19 Pallipadi, Venkatesh
2005-12-04 16:46 ` Dominik Brodowski
2005-12-05 11:00 ` Bruno Ducrot
2005-12-06 6:01 ` Dominik Brodowski
2005-12-06 10:03 ` Bruno Ducrot
2005-12-06 10:10 ` Dominik Brodowski
2005-12-02 16:58 Pallipadi, Venkatesh
2005-12-02 19:29 ` Felix Braun
2005-12-02 21:06 ` Bruno Ducrot
2005-12-02 13:57 Felix Braun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051202155235.1e83e932@tilion.getrex.org \
--to=felix.braun@mail.mcgill.ca \
--cc=CPUFreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=linux@dominikbrodowski.net \
--cc=venkatesh.pallipadi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.