From: Thomas Andrews <tandrews-Dza9YrynN5pWaveUIWBRJg@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Starting AML
Date: Thu, 29 Apr 2004 21:21:33 +0200 [thread overview]
Message-ID: <20040429192133.GI28420@gaspode.nextlink.co.za> (raw)
Hi Everyone,
I want to try to understand how to debug my DSDT properly, so I'd
appreciate some hints for debugging. I've started reading through the
ACPI specification available at http://www.acpi.info/spec.htm
Firstly, how do I find out in the AML where the relevant pieces of code
are ? For example, the battery voltage reported is wrong; how do I figure
out which bits to edit ?
Secondly, how can I output debugging messages ? Is there some way I can
use something like printf/printk ?
I have already fixed the "syntax errors" produced by compiling the
original BIOS DSDT. That didn't fix anything BTW.
I have also read the (very helpful) docs and howtos on SF. Thanks.
The laptop is a Compaq Evo N150, for which there seem to be no fixes
made public.
Many thanks,
Thomas
-------------------------------------------------------
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
next reply other threads:[~2004-04-29 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 19:21 Thomas Andrews [this message]
[not found] ` <20040429192133.GI28420-beYWCVBHuyQmjp9Ioln+9+7fARiR49SZ@public.gmane.org>
2004-04-29 21:59 ` Starting AML Franklin Marmon
2004-04-30 6:46 ` Zdeněk OGAR Skalák
[not found] ` <4091F662.EF7F0B1C-Bh/+Xfn7orxQjibfaplwYw@public.gmane.org>
2004-05-01 9:23 ` Thomas Andrews
[not found] ` <20040501092338.GA17352-beYWCVBHuyQmjp9Ioln+9+7fARiR49SZ@public.gmane.org>
2004-05-01 10:43 ` Thomas Andrews
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=20040429192133.GI28420@gaspode.nextlink.co.za \
--to=tandrews-dza9yrynn5pwaveuiwbrjg@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