From: Pavel Machek <pavel@suse.cz>
To: Dominik Brodowski <linux@brodo.de>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
hpa@zytor.com, cpufreq@www.linux.org.uk
Subject: Re: cpufreq patches for 2.5.39 follow
Date: Mon, 30 Sep 2002 02:38:51 +0000 [thread overview]
Message-ID: <20020930023850.E35@toy.ucw.cz> (raw)
In-Reply-To: <20020928112130.A1217@brodo.de>; from linux@brodo.de on Sat, Sep 28, 2002 at 11:21:30AM +0200
Hi!
> The interface to userspace is /proc/cpufreq, and the user can "echo" a new
> policy into this file using the following syntax:
> [cpu:]min_freq:max_freq:policy or
> [cpu%]min_pctg%max_pctg%policy
Should we have both in kernel?
How does it interact with ACPI? Ie. I do echo "100%100%foo", but ACPI thermal
managment decides to slow down?
> Patch 3/5: cpufreq-i386-drivers
> -------------------------------
> Six i386 CPUFreq drivers are ready to be merged this time. These are:
> elanfreq.c: The AMD Elan CPU family offers extensive clock scaling
> longhaul.c: VIA Longhaul processor clock + voltage scaling
> longrun.c: Transmeta Crusoe Longrun clock + voltage scaling
> p4-clockmod.c: clock modulation on P4 Xeon processors
> powernow-k6.c: mobile AMD K6-2+ / mobile AMD K6-3+ clock scaling
> speedstep.c: clock and voltage scaling on mobile Intel Pentium 3 and 4s,
> but (unfortunately) only on ICH2-M or ICH3-M based
> chipsets.
>
> Support for mobile AMD K7 processors is still in development.
What about mobile celerons?
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2002-10-01 22:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 9:21 Dominik Brodowski
2002-09-30 2:38 ` Pavel Machek [this message]
2002-10-02 1:22 ` Alan Cox
2002-10-01 22:55 Grover, Andrew
2002-10-01 22:59 ` Pavel Machek
2002-10-01 23:07 Grover, Andrew
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=20020930023850.E35@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=cpufreq@www.linux.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®