From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Andrews Subject: Starting AML Date: Thu, 29 Apr 2004 21:21:33 +0200 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <20040429192133.GI28420@gaspode.nextlink.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org 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