From: Erik Slagter <erik@slagter.name>
To: linux-acpi@vger.kernel.org
Subject: c1/c1e/c3/c6/c7 on linux
Date: Sun, 22 Nov 2009 12:46:16 +0100 [thread overview]
Message-ID: <4B092488.5040801@slagter.name> (raw)
In-Reply-To: <4B06A7A8.109@slagter.name>
Ik have two machines, a dell laptop with a mobile core2duo T9300 and a
gigabyte desktop with a core i7 920. Both advertise all of these
C-states c1/c1e/c3/c6/c7 in the specs (although the core2duo doesn't
have c7 I believe).
It's not clear at all how linux handles these. The kernel on the T9300
says it uesde C1/C2/C3 of "type" C1/C2/C3, the core i7 says exactly the
same.
Is this a WiP? A bios issue? It looks like I am missing some states?
The kernel I am using is 2.6.31.6
next prev parent reply other threads:[~2009-11-22 11:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 14:28 No c2-c7 states on core i7 Erik Slagter
2009-11-21 17:45 ` Erik Slagter
2009-11-22 11:46 ` Erik Slagter [this message]
2009-11-23 3:05 ` ykzhao
2009-11-23 8:52 ` Erik Slagter
2009-11-23 16:11 ` Len Brown
2009-11-23 19:23 ` Erik Slagter
2009-11-23 19:26 ` Erik Slagter
2009-11-24 13:34 ` Jindrich Makovicka
2009-11-24 13:55 ` Erik Slagter
2009-11-25 6:59 ` Len Brown
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=4B092488.5040801@slagter.name \
--to=erik@slagter.name \
--cc=linux-acpi@vger.kernel.org \
/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