public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Hughes <tom@compton.nu>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Thomas Renninger <trenn@suse.de>,
	acpi4asus-user@lists.sourceforge.net,
	Dave Jones <davej@redhat.com>,
	Cristiano Prisciandaro <cristiano.p@solnet.ch>,
	linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org
Subject: Re: [Acpi4asus-user] [PATCH 1/1] cpufreq: eeepc 900 frequency scaling driver
Date: Mon, 24 Nov 2008 17:07:42 +0000	[thread overview]
Message-ID: <492ADF5E.2050709@compton.nu> (raw)
In-Reply-To: <71cd59b00811240858p3b830c73qc2742023d2977054@mail.gmail.com>

Corentin Chary wrote:

> Just modprobe p4-clockmod
> - use cpufreq to go to the lower frequency
> - run something cpu intensive
> - go to the higher frequency (900mghz)
> - you'll see the difference
> 
> at least, it works with my eeepc 700, maybe 900 is different for that,
> but it seems unlikely to me.

Have a look at http://www.codemonkey.org.uk/projects/eeepc/ for an 
explanation of what p4-clockmod does and why it isn't really changing 
the speed of the processor (but does cause you to get less work done).

tom

-- 
Tom Hughes (tom@compton.nu)
http://www.compton.nu/

  reply	other threads:[~2008-11-24 17:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23 15:27 [PATCH 1/1] cpufreq: eeepc 900 frequency scaling driver Cristiano Prisciandaro
2008-11-23 18:04 ` Pavel Machek
2008-12-02 16:15   ` Matthew Garrett
2008-12-02 20:14     ` Pavel Machek
2009-03-16  4:24       ` Len Brown
2009-03-16  8:29         ` Pavel Machek
2009-03-17  8:30           ` Fabio Comolli
2009-03-17  8:59             ` Fabio Comolli
2008-11-24  9:38 ` Tom Hughes
2008-11-24 15:13   ` Thomas Renninger
2008-11-24 16:36     ` Thomas Renninger
2008-11-24 16:41       ` [Acpi4asus-user] " Corentin Chary
2008-11-24 16:48         ` Tom Hughes
2008-11-24 16:58           ` Corentin Chary
2008-11-24 17:07             ` Tom Hughes [this message]
2008-11-24 16:46       ` Tom Hughes
2008-11-24 23:02       ` Cristiano Prisciandaro
2009-04-05  7:43         ` [Acpi4asus-user] " Corentin Chary
2009-04-05 10:20           ` Matthew Garrett
2009-04-05 11:39             ` Grigori Goronzy
2008-11-24 16:39     ` Tom Hughes
2008-11-24 19:09   ` Cristiano Prisciandaro
2008-12-03 19:26   ` Tom Hughes
2008-12-04  1:57     ` Thomas Renninger
2008-12-05 23:05       ` Tom Hughes
2008-12-06 16:35         ` Matthew Garrett
2008-12-07 15:55           ` Tom Hughes
2008-12-09 12:36             ` Pavel Machek

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=492ADF5E.2050709@compton.nu \
    --to=tom@compton.nu \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=corentin.chary@gmail.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=cristiano.p@solnet.ch \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trenn@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox