From: Lee Revell <rlrevell@joe-job.com>
To: Paulo Marques <pmarques@grupopie.com>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Andi Kleen <ak@suse.de>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add p4-clockmod driver in x86-64
Date: Wed, 27 Oct 2004 11:56:27 -0400 [thread overview]
Message-ID: <1098892587.8313.5.camel@krustophenia.net> (raw)
In-Reply-To: <417FB7BA.9050005@grupopie.com>
On Wed, 2004-10-27 at 15:59 +0100, Paulo Marques wrote:
> I am one of the members of the robotic soccer team from the University
> of Oporto, and a couple of months ago we were looking for new
> motherboards for our robots, because we are starting to need new
> hardware (on-board lan, usb2.0, etc.).
>
> We really don't need excepcional performance, but we really, really need
> low power consumption, so lowering the clock on a standard mainboard
> seemed to be the best cost/performance scenario.
>
> Could this driver be used to keep a standard p4 processor at say 25%
> clock speed at all times?
>
Why don't you try the VIA EPIA mini-ITX boards? These are designed for
low power applications like yours. I am running the M-6000 which has a
fanless 600Mhz C3 processor, the newer fanless models run at 1Ghz. And,
on top of that they support speed scaling so you can slow it down even
more.
Lee
next prev parent reply other threads:[~2004-10-27 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 14:43 [PATCH] Add p4-clockmod driver in x86-64 Pallipadi, Venkatesh
2004-10-27 14:59 ` Paulo Marques
2004-10-27 15:56 ` Lee Revell [this message]
2004-10-27 16:14 ` Paulo Marques
2004-10-27 16:22 ` Alan Cox
2004-10-27 18:47 ` Marcus Metzler
2004-10-27 21:38 ` Rutger Nijlunsing
2004-10-27 21:50 ` Alan Cox
2004-10-28 0:17 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2004-10-27 16:39 Pallipadi, Venkatesh
2004-10-26 21:28 Venkatesh Pallipadi
2004-10-27 3:18 ` Andi Kleen
2004-10-28 0:10 ` Andi Kleen
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=1098892587.8313.5.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.com \
--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.