From: Cam <camilo-Nk/s8sJ9yP7QXOPxS62xeg@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: annotated DSDT, anyone?
Date: Sat, 29 May 2004 12:48:53 +0100 [thread overview]
Message-ID: <40B878A5.7020806@mesias.co.uk> (raw)
Hi
I have a laptop with partially working ACPI support and I hope to patch
it. I have been reading the Intel manuals on ACPI and AML and looking at
patches on the internet for various DSDT problems.
I have started to try to figure out my own DSDT and wondered if there
are any DSDT disassembled out there with annotations, I think that would
be helpful to understand them. Any suggestions?
Also are there any FAQs about how to understand the contents of the
DSDT, maybe to find out locations in the PCI config space that could be
peeked or poked with pcitweak? Is there any way to examine ACPI
variables on a running system?
-Cam
-------------------------------------------------------
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
reply other threads:[~2004-05-29 11:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40B878A5.7020806@mesias.co.uk \
--to=camilo-nk/s8sj9yp7qxopxs62xeg@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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