From: Jan Slezak <jan.slezak-aRb0bU7PRFPrBKCeMvbIDA@public.gmane.org>
To: acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Cc: Marco Walther <Marco.Walther-xsfywfwIY+M@public.gmane.org>,
James D Strandboge
<jstrand1-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.org>
Subject: Dell DSDT corrected
Date: Tue, 28 Jan 2003 11:20:15 +0100 [thread overview]
Message-ID: <200301281120.15917.jan.slezak@centrum.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
Hi there!
I modified my Dell Latitude C640 DSDT table and values in /proc/acpi what were
previously constantly zero (or something equivalent) where brought to life.
This is:
- temperature in thermal zone
- processor frequency in performance in processor (processor consumption is
still zero, but I belive it is not exposed to ACPI)
- all information in battery (except presence/absence what was already working
before)
The DSDT patch and original DSDT are enclosed I hope it helps someone.
Patch avoids passing buffers as arguments to functions that modifies it. I
discovered that such buffers are passed by value and modifications don't
apply to where it should.
P.S. to Marco: I didn't find any item in my DSDT concerning fans so I think it
is realy not exposed to ACPI and no items are shown under /proc/acpi/fan
(WinXP also doesn't show fans in hardware list and I think it doesn't drive
them, they are likely driven directly by BIOS). But I am able to drive fans
by i8k module made by Massimo Dal Zotto.
Jan
[-- Attachment #2: dsdt.dsl.dell.gz --]
[-- Type: application/x-gzip, Size: 8204 bytes --]
[-- Attachment #3: dsdt.dsl.dell.patch.gz --]
[-- Type: application/x-gzip, Size: 748 bytes --]
next reply other threads:[~2003-01-28 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 10:20 Jan Slezak [this message]
[not found] ` <200301281120.15917.jan.slezak-aRb0bU7PRFPrBKCeMvbIDA@public.gmane.org>
2003-01-29 18:04 ` Dell DSDT corrected Markus Wiesner
[not found] ` <20030129180444.GB10601-aCYJ90g6FbN3mO1V46hDx7oZL2q1Rlic@public.gmane.org>
2003-01-30 15:45 ` Is this safe? " James D Strandboge
[not found] ` <1043878640.1471.6.camel@sirius.strandboge.cxm>
[not found] ` <20030129230247.GB11019@homerelay.wiesner-net.de>
[not found] ` <1043883259.3421.7.camel@sirius.strandboge.cxm>
[not found] ` <20030130220318.GA12147@homerelay.wiesner-net.de>
[not found] ` <20030130220318.GA12147-aCYJ90g6FbN3mO1V46hDx7oZL2q1Rlic@public.gmane.org>
2003-01-31 4:30 ` Is this safe? James D Strandboge
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=200301281120.15917.jan.slezak@centrum.cz \
--to=jan.slezak-arb0bu7prfprbkcemvbida@public.gmane.org \
--cc=Marco.Walther-xsfywfwIY+M@public.gmane.org \
--cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org \
--cc=jstrand1-aYIB8uWIUb2Vn7q6wjsIow@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