From: Franklin Marmon <marmon-a4VQZhDi8cxBDgjK7y7TUQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Starting AML
Date: Thu, 29 Apr 2004 15:59:32 -0600 [thread overview]
Message-ID: <1083275971.4976.67.camel@laptop.hydeco.com> (raw)
In-Reply-To: <20040429192133.GI28420-beYWCVBHuyQmjp9Ioln+9+7fARiR49SZ@public.gmane.org>
I'm pretty new to ACPI in general, but I might recommend reading chapter
11 of the spec. It lays out in detail what parts of the code you should
be looking in. If your not familiar with the layout of the asm itself,
I'm not sure where to point you, but someone else probably is. I just
read the first few chapters of the spec and 'logiced' out the rest,
which will likely result in a broken system in my case, but that remains
to be seen.
You will likely be looking at the _BIF method of your battery device.
This is the method that returns (by the spec anyway) static information
about your battery, including the design voltage. The battery device
name is different depending on your hardware, but is fairly easy to find
if you search for "_BIF" in the aml.
As far as debugging the DSDT, not a clue. I'm pretty sure you can't use
kernel calls within the DSDT asm code. So, my best guess if your sure
your DSDT is wrong is to correct the changes, compile it into the
kernel, and re-check your /proc/acpi/... data.
frm
On Thu, 2004-04-29 at 13:21, Thomas Andrews wrote:
> 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
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>
-------------------------------------------------------
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 prev parent reply other threads:[~2004-04-29 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 19:21 Starting AML Thomas Andrews
[not found] ` <20040429192133.GI28420-beYWCVBHuyQmjp9Ioln+9+7fARiR49SZ@public.gmane.org>
2004-04-29 21:59 ` Franklin Marmon [this message]
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=1083275971.4976.67.camel@laptop.hydeco.com \
--to=marmon-a4vqzhdi8cxbdgjk7y7tuq@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