public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
Cc: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH][RFC] Add C3 support to P4-M / ICH-M chipsets
Date: 20 May 2004 23:34:11 -0400	[thread overview]
Message-ID: <1085110450.12353.553.camel@dhcppc4> (raw)
In-Reply-To: <20040518211431.GA17545-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>

On Tue, 2004-05-18 at 17:14, Karol Kozimor wrote:

> Now, for the tricky part:
> 
> 1) Is it actually worth it? Do the power savings justify the effort? Are
>    there many people who might benefit from this patch?
> 2) Are there any chances on merging such chipset-specific quirks?
>    Obviously, not in the current form, but possibly as a separate object
>    surrounded by pci_find_subsys() or anything appropriate?

Karol,
Good hunting ont he chip set spect etc.

But lets wait till after we have a _CST based implementation in place
and then see if the workarounds are still necessary then.

thanks,
-Len




-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click

  parent reply	other threads:[~2004-05-21  3:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18 21:14 [PATCH][RFC] Add C3 support to P4-M / ICH-M chipsets Karol Kozimor
     [not found] ` <20040518211431.GA17545-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-05-21  3:34   ` Len Brown [this message]
     [not found]     ` <1085110450.12353.553.camel-D2Zvc0uNKG8@public.gmane.org>
2004-05-21 18:01       ` Bruno Ducrot
     [not found]         ` <20040521180155.GP29214-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-05-21 19:42           ` Karol Kozimor
     [not found]             ` <20040521194205.GA25863-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-05-24 10:11               ` Bruno Ducrot
     [not found]                 ` <20040524101130.GB4387-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-05-24 10:59                   ` Karol Kozimor
  -- strict thread matches above, loose matches on Subject: below --
2004-05-26  3:06 Yu, Luming

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=1085110450.12353.553.camel@dhcppc4 \
    --to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=sziwan-DETuoxkZsSqrDJvtcaxF/A@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