From: David Moore <dcm-HInyCGIudOg@public.gmane.org>
To: "Adachi,
Kenichi"
<adachi-fvZ7ij+YLgEZc9YY0SgeQc8NsWr+9BEh@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: RE: _PDC method in DSDT
Date: 22 Jun 2003 21:17:25 -0700 [thread overview]
Message-ID: <1056341845.10322.44.camel@aldebaran.caltech.edu> (raw)
In-Reply-To: <00be01c33922$b8fb3cd0$b8d21b2b-5Bsh/8v8vXc@public.gmane.org>
Thanks, that's exactly what I needed.
Given this document, I think I have enough information now to patch
processor.c to support Enhanced Speedstep on Pentium M for those BIOSes
that have a correctly written _PDC method in the DSDT. Would the
maintainers of the ACPI driver be willing to accept such a patch?
Regards,
David
On Sun, 2003-06-22 at 17:59, Adachi, Kenichi wrote:
> Hi,
>
> > Does anyone know the purpose or specification of the _PDC method of
> the DSDT?
>
> It's another annoyance (?) added by Microsoft -);
> Document is available online at the following URL:
>
> "Windows Native Processor Performance Control"
> http://www.microsoft.com/whdc/hwdev/tech/onnow/procperfctrl.mspx
>
> Thanks,
> - Adachi, Kenichi
>
-------------------------------------------------------
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
next prev parent reply other threads:[~2003-06-23 4:17 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 [this message]
2003-06-23 10:07 ` Ducrot Bruno
[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=1056341845.10322.44.camel@aldebaran.caltech.edu \
--to=dcm-hinycgiudog@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=adachi-fvZ7ij+YLgEZc9YY0SgeQc8NsWr+9BEh@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