From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: Valerio Felici <valerio-3NZjWNnCfY8@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Error in dsdt from asus a3527nuh
Date: Tue, 09 Nov 2004 12:49:44 -0800 [thread overview]
Message-ID: <41912D68.8040609@root.org> (raw)
In-Reply-To: <200411092131.27258.valerio-3NZjWNnCfY8@public.gmane.org>
Valerio Felici wrote:
> Sorry in advance if this is the wrong ml for my question, or if this one is
> bad formed.
>
> I've a new asus a3527nuh. I've decompiled my dsdt and trying to compile it
> with iasl I can observe there is an error, it seems a stupid error, but I'm
> not able to solve it.
>
> So I've decide to post it here in attachment (tar-gzipped) so someone can,
> perhaps, debug it better than me.
>
> Notebook is ASUS A3N family
> Bios is 0205 version
>
> Iasl Report:
> -----
> # iasl -tc dsdt.dsl
>
> Intel ACPI Component Architecture
> ASL Optimizing Compiler / AML Disassembler version 20040527 [May 27 2004]
> Copyright (C) 2000 - 2004 Intel Corporation
> Supports ACPI Specification Revision 2.0c
>
> dsdt.dsl 7818: If (SS1)
> Error 1037 - ^ parse error
>
> ASL Input: dsdt.dsl - 7924 lines, 271634 bytes, 3603 keywords
> Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 0 Optimizations
I don't know if this is the same problem but I've noticed a lot of
systems with AML opcodes outside any method. This is technically
illegal but iasl should still be able to handle it.
--
Nate
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next prev parent reply other threads:[~2004-11-09 20:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 20:31 Error in dsdt from asus a3527nuh Valerio Felici
[not found] ` <200411092131.27258.valerio-3NZjWNnCfY8@public.gmane.org>
2004-11-09 20:49 ` Nate Lawson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-09 20:54 Moore, Robert
[not found] ` <37F890616C995246BE76B3E6B2DBE0550294974F-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org >
2004-11-10 17:05 ` valerio-3NZjWNnCfY8
[not found] <37F890616C995246BE76B3E6B2DBE05502982B70@orsmsx403.amr.corp.intel.com>
[not found] ` <37F890616C995246BE76B3E6B2DBE05502982B70-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-11-11 14:35 ` Valerio Felici
2004-11-11 14:45 Yu, Luming
2004-11-11 14:58 ` Valerio Felici
2004-11-11 15:07 Yu, Luming
2004-11-11 16:58 ` Valerio Felici
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=41912D68.8040609@root.org \
--to=nate-y6vguytwhu0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=valerio-3NZjWNnCfY8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.