From: Dave Jones <davej@redhat.com>
To: cpufreq@www.linux.org.uk
Subject: ACPI / CPUFREQ.
Date: Tue, 3 Aug 2004 16:10:11 +0100 [thread overview]
Message-ID: <20040803151010.GQ12724@redhat.com> (raw)
At his ACPI talk at OLS, Len mentioned that it would be beneficial
to have ACPI and CPUFREQ working together a little better.
Len, care to kick off some thoughts on what pieces you had in mind ?
The biggest problem is probably ACPI thinking the CPU should be at a
certain P-state whilst the user has forced it to another with cpufreq.
Dave
next reply other threads:[~2004-08-03 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 15:10 Dave Jones [this message]
2004-08-03 15:41 ` ACPI / CPUFREQ Len Brown
2004-08-03 20:51 ` Dominik Brodowski
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=20040803151010.GQ12724@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@www.linux.org.uk \
/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