From: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: eric.piel-VkQ1JFuSMpfAbQlEx87xDw@public.gmane.org
Cc: len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] ACPI/Processor: C1/C3 states promotion and demotion
Date: Tue, 10 Feb 2004 21:07:06 +0100 [thread overview]
Message-ID: <20040210200706.GJ13262@poupinou.org> (raw)
In-Reply-To: <1076335639.40279417dabd5-cj29PWmZ5eXjVsaOS7U83g@public.gmane.org>
On Mon, Feb 09, 2004 at 03:07:19PM +0100, eric.piel-VkQ1JFuSMpfAbQlEx87xDw@public.gmane.org wrote:
> Hello,
>
> Some processors seems to support only C1 and C3 states, for instance... mine ;-)
> (Pentium III Coppermine). The problem is that, in this case, no promotion or
> demotion are linking those two states, therefore the preocessor never goes to C3!
>
There is no intel-like processors for which there is C3, but no C2. So
you have actually to fake a C2 (which should be at a latency of 30 IIRC).
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-02-10 20:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 14:07 [PATCH] ACPI/Processor: C1/C3 states promotion and demotion eric.piel-VkQ1JFuSMpfAbQlEx87xDw
[not found] ` <1076335639.40279417dabd5-cj29PWmZ5eXjVsaOS7U83g@public.gmane.org>
2004-02-10 20:07 ` Bruno Ducrot [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-10 3:21 Ow Mun Heng
[not found] ` <C386328088ED7F4E9F81AFBABDDF60DA03F9E5A8-Yw6hFe9C1vnHQcBQSaPqJq0fmWJ9l57d0E9HWUfgJXw@public.gmane.org>
2004-02-10 9:17 ` eric.piel-VkQ1JFuSMpfAbQlEx87xDw
2004-02-10 9:36 Ow Mun Heng
[not found] ` <C386328088ED7F4E9F81AFBABDDF60DA03F9E637-Yw6hFe9C1vnHQcBQSaPqJq0fmWJ9l57d0E9HWUfgJXw@public.gmane.org>
2004-02-10 9:52 ` eric.piel-VkQ1JFuSMpfAbQlEx87xDw
2004-02-11 2:19 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB68C-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-11 8:25 ` eric.piel-VkQ1JFuSMpfAbQlEx87xDw
2004-02-11 11:03 ` Bruno Ducrot
2004-02-11 11:37 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB6A1-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-11 12:22 ` Bruno Ducrot
2004-02-12 3:49 Yu, Luming
2004-02-12 4:00 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB6AB-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-12 9:57 ` Bruno Ducrot
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=20040210200706.GJ13262@poupinou.org \
--to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=eric.piel-VkQ1JFuSMpfAbQlEx87xDw@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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