From: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
To: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Cc: Rich Townsend <rhdt-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>,
Stefan Seyfried
<seife-T+3qhDtrTvDv8lqoKu5MV4HBZQ1bDw0s@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
scotch-cGBD8117FJM@public.gmane.org
Subject: Re: Re: _CST implementation
Date: Fri, 22 Apr 2005 15:00:34 +0200 [thread overview]
Message-ID: <4268F572.4090707@suse.de> (raw)
In-Reply-To: <20050420094556.GN2298-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Bruno Ducrot wrote:
> On Tue, Apr 19, 2005 at 04:11:45PM -0400, Rich Townsend wrote:
>>Stefan Seyfried wrote:
>>>On Tue, Apr 19, 2005 at 03:45:18PM +0200, Bruno Ducrot wrote:
>>>
>>>
>>>>IOW, from spec we should not invalidate, but from "common practice" by
>>>>bios writters, we should invalidate.
>>>
>>>What about a "spec_compliant_but_beware_of_stupid_bios_writers" module
>>>parameter? ;-)
>>I fear that would be set to nonzero on every system...
>>
>
> That's the case already. This is the boot parameter
> acpi=strict
I do not think it is a good idea to make this depend on acpi=strict.
Normally !acpi_strict enables features for some broken BIOS.
In this case !acpi_strict disables them.
There still is max_cstates if something goes terribly wrong.
I never saw such a machine, are there many of them out there?
Janosch: Did you get the 1001 latency state to work?
Thomas
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-04-22 13:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 20:50 _CST implementation Janosch Machowinski
2005-04-18 12:07 ` Bruno Ducrot
[not found] ` <20050418120744.GG2298-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-04-18 12:23 ` Janosch Machowinski
2005-04-18 14:21 ` Bruno Ducrot
2005-04-18 17:25 ` Thomas Renninger
[not found] ` <4263EDA2.4030106-l3A5Bk7waGM@public.gmane.org>
2005-04-18 17:52 ` Janosch Machowinski
2005-04-19 9:22 ` Bruno Ducrot
[not found] ` <20050419092251.GK2298-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-04-19 11:58 ` Thomas Renninger
[not found] ` <4264F251.5030705-l3A5Bk7waGM@public.gmane.org>
2005-04-19 13:45 ` Bruno Ducrot
[not found] ` <20050419134518.GL2298-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-04-19 20:05 ` Stefan Seyfried
[not found] ` <20050419200505.GE19499-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2005-04-19 20:11 ` Rich Townsend
[not found] ` <42656601.3060304-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
2005-04-20 9:45 ` Bruno Ducrot
[not found] ` <20050420094556.GN2298-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-04-22 13:00 ` Thomas Renninger [this message]
[not found] ` <4268F572.4090707-l3A5Bk7waGM@public.gmane.org>
2005-04-22 17:13 ` Janosch Machowinski
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=4268F572.4090707@suse.de \
--to=trenn-l3a5bk7wagm@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org \
--cc=rhdt-OBnUx95tOyn10jlvfTC4gA@public.gmane.org \
--cc=scotch-cGBD8117FJM@public.gmane.org \
--cc=seife-T+3qhDtrTvDv8lqoKu5MV4HBZQ1bDw0s@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