From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: Thomas Renninger <mail-smMupaH/RwJM7kwft8N7nw@public.gmane.org>
Cc: ML ACPI-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: ASUS M6800N: processor has only C1
Date: Wed, 10 Mar 2004 20:17:24 -0800 (PST) [thread overview]
Message-ID: <20040310201438.Y61960@root.org> (raw)
In-Reply-To: <40471F8E.5080308-smMupaH/RwJM7kwft8N7nw@public.gmane.org>
On Thu, 4 Mar 2004, Thomas Renninger wrote:
> Thomas Renninger wrote:
> > Your machine supports the C4 state.
> > Change the P_BLK in your DSDT to 0x06
> >
> > e.g.:
> > Processor (\_PR.CPU0, 0x01, 0x00001010, 0x07)
> > to:
> > Processor (\_PR.CPU0, 0x01, 0x00001010, 0x06)
> >
> > or use the patch from Pavel, posted on the 28.02.2004, 17:10.
> >
> > Unfortunately this won't enable the C4 state if you have one.
> > What do mainters say about supporting Cn processor states in the future?
>
> I am pretty sure this message will come up more often in future.
> Could it be that new mobile Intel processors support the C4 state ->
> therefore P_BLK = 0x07?
>
> Pavel's patch is a workaround, setting P_BLK back to 6, but isn't it
> worth a critical bug for supporting Cn states,
> as only supporting C0-C3 states offends the specification?
For FreeBSD, I took the approach that throttling requires P_BLK_LEN >= 4,
C2 requires >= 5, and C3 requires >= 6. Systems with higher values will
get C1-C3 but we will not support C4 on such systems. There are already
plenty of valid systems with _CST out in the real world (i.e. IBM Centrino
laptops) and so for someone to break the standard now is unacceptable.
Users will get C1-C3 on broken systems, which is good enough.
-Nate
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-11 4:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 9:55 ASUS M6800N: processor has only C1 Luca Capello
[not found] ` <404459FD.1000406-wlebWZzHoyE@public.gmane.org>
2004-03-02 11:09 ` Bruno Ducrot
[not found] ` <20040302110946.GF2869-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-03-02 12:43 ` Luca Capello
[not found] ` <40448169.6090507-wlebWZzHoyE@public.gmane.org>
2004-03-02 14:43 ` Luca Capello
[not found] ` <40449D8E.4060402-wlebWZzHoyE@public.gmane.org>
2004-03-03 10:35 ` Bruno Ducrot
[not found] ` <20040303103528.GG2869-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-03-03 20:18 ` Luca Capello
[not found] ` <40463D80.8040800-wlebWZzHoyE@public.gmane.org>
2004-03-04 11:12 ` Bruno Ducrot
[not found] ` <20040304111240.GN2869-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-03-04 13:53 ` Luca Capello
[not found] ` <404734E8.7080104-wlebWZzHoyE@public.gmane.org>
2004-03-05 11:39 ` Bruno Ducrot
[not found] ` <20040305113921.GS2869-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-03-05 15:42 ` Luca Capello
[not found] ` <40489FC8.4000605-wlebWZzHoyE@public.gmane.org>
2004-03-05 18:37 ` Bruno Ducrot
[not found] ` <20040305183737.GT2869-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-03-05 20:21 ` Luca Capello
2004-03-04 11:45 ` Bruno Ducrot
2004-03-04 12:00 ` Thomas Renninger
[not found] ` <40471A4F.2090909-smMupaH/RwJM7kwft8N7nw@public.gmane.org>
2004-03-04 12:22 ` Thomas Renninger
[not found] ` <40471F8E.5080308-smMupaH/RwJM7kwft8N7nw@public.gmane.org>
2004-03-11 4:17 ` Nate Lawson [this message]
2004-03-04 12:36 ` Thomas Renninger
2004-03-05 17:49 ` Luca Capello
2004-03-20 10:29 ` Luca Capello
[not found] ` <405C1D0F.3030209-wlebWZzHoyE@public.gmane.org>
2004-03-20 17:27 ` Herman Sheremetyev
[not found] ` <1079803656.32419.15.camel-l85cmlzfk8I@public.gmane.org>
2004-03-20 18:39 ` Luca Capello
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=20040310201438.Y61960@root.org \
--to=nate-y6vguytwhu0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mail-smMupaH/RwJM7kwft8N7nw@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