From: Eric Piel <Eric.Piel-VkQ1JFuSMpfAbQlEx87xDw@public.gmane.org>
To: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Cc: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>,
len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATHC] Relaxed syntax for the processor PBLK length
Date: Mon, 31 Jan 2005 16:44:48 +0100 [thread overview]
Message-ID: <41FE5270.8030605@tremplin-utc.net> (raw)
In-Reply-To: <20050131152931.GC1145-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Bruno Ducrot a écrit :
> On Mon, Jan 31, 2005 at 04:11:59PM +0100, Eric Piel wrote:
>
>>Why? Actually this patch is especially designed to allow C3 state to be
>>used on my computer. This works for more than 6 months without any
>>appearent problem, is there anything I'm not aware of?
>
>
> I thought some BIOS devellopers wanted to use a size for the
> pblk of 5 just to not allow C3 (which correspond to the sixth io
> register).
>
> I'm not alone to think this.
>
> Nate: FreeBSD allow only C2 in this case. What do you think about this
> report?
> Do you have an example of some kind of malfunction when enabling C3?
Actually in the DSDT the C2 seems really deactivated (latency is set to
the maximum, something like 999 ms) while C3 has a declared latency that
seems realistic. Additionally, in the C3 state, the computer works
perfectly.
Is there anyway in Windows to check if it uses a particular C state?
Eric
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-31 15:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 20:05 [PATHC] Relaxed syntax for the processor PBLK length Eric Piel
[not found] ` <41FD3E02.8010701-VkQ1JFuSMpfAbQlEx87xDw@public.gmane.org>
2005-01-30 21:39 ` Johan Vromans
2005-01-30 22:43 ` Richard Dawe
2005-01-31 14:58 ` Bruno Ducrot
[not found] ` <20050131145836.GA1145-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-01-31 15:11 ` Eric Piel
[not found] ` <41FE4ABF.9040100-VkQ1JFuSMpfAbQlEx87xDw@public.gmane.org>
2005-01-31 15:29 ` Bruno Ducrot
[not found] ` <20050131152931.GC1145-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-01-31 15:44 ` Eric Piel [this message]
2005-01-31 15:47 ` Herman Sheremetyev
2005-01-31 15:59 ` Dominik Brodowski
[not found] ` <20050131155917.GA4416-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2005-01-31 16:14 ` Eric Piel
[not found] ` <41FE595D.5020605-VkQ1JFuSMpfAbQlEx87xDw@public.gmane.org>
2005-01-31 16:26 ` Dominik Brodowski
[not found] ` <20050131162628.GA4911-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2005-01-31 16:29 ` Dominik Brodowski
2005-01-31 16:36 ` Bruno Ducrot
[not found] ` <20050131163603.GE1145-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-01-31 18:53 ` 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=41FE5270.8030605@tremplin-utc.net \
--to=eric.piel-vkq1jfusmpfabqlex87xdw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=nate-Y6VGUYTwhu0@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