public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: David Moore <dcm-HInyCGIudOg@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: _PDC method in DSDT
Date: Mon, 23 Jun 2003 12:07:44 +0200	[thread overview]
Message-ID: <20030623100744.GU19556@poupinou.org> (raw)
In-Reply-To: <1056329130.10322.36.camel-cfibRQahR+cF6I9xFAAkN5QCsf4PZ8us@public.gmane.org>

On Sun, Jun 22, 2003 at 05:45:31PM -0700, David Moore wrote:
> Hi,
> 
> Does anyone know the purpose or specification of the _PDC method of the
> DSDT?  It's a reserved method that exists on my laptop (a Dell Latitude
> D600) but does not seem to be documented in the ACPI specification on
> the web.
> 
> The reason I ask is that I'm interested in porting the cpufreq driver
> for Enhanced Speedstep to ACPI.  Right now, the cpufreq driver has the
> tables of proper MSR register values encoded into the source, but a more
> elegant solution would be to get this information from ACPI.  In my DSDT
> source I notice that when the _PDC method is called properly, the _PCT
> method will return FixedHardware addresses for the Enhanced Speedstep
> MSRs instead of its normal SystemIO ports.  To get this to work on more
> than just my system, I should probably use the proper specification for
> calling _PDC rather than just making it work.
> 
> Anyone have any suggestions?
> 


Too late...  A CPUFreq driver is already writen and is in the CPUFreq cvs.

-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php

  parent reply	other threads:[~2003-06-23 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23  0:45 _PDC method in DSDT David Moore
     [not found] ` <1056329130.10322.36.camel-cfibRQahR+cF6I9xFAAkN5QCsf4PZ8us@public.gmane.org>
2003-06-23  0:59   ` Adachi, Kenichi
     [not found]     ` <00be01c33922$b8fb3cd0$b8d21b2b-5Bsh/8v8vXc@public.gmane.org>
2003-06-23  4:17       ` David Moore
2003-06-23 10:07   ` Ducrot Bruno [this message]
     [not found]     ` <20030623100744.GU19556-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-06-23 11:51       ` Ducrot Bruno

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=20030623100744.GU19556@poupinou.org \
    --to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=dcm-HInyCGIudOg@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