public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Feldmann <feldmann_markus@gmx.de>
To: Alexey Starikovskiy <aystarik@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITIONBLOCK
Date: Tue, 01 May 2007 20:43:02 +0200	[thread overview]
Message-ID: <46378A36.7080108@gmx.de> (raw)
In-Reply-To: <8f8ff01d0705010638x5d4d398dk6f754e1f2cd2198a@mail.gmail.com>

Alexey Starikovskiy schrieb:
> Please remove error lines at the beginning of the file and try to
> compile it again...
> 
Ok here it comes the corrected dsdt_2.6.21.dsl file with the new error
messages,

feld-bertlap:~/acpi/dsdt# iasl -tc dsdt_2.6.21.dsl

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20060912 [Dec 20 2006]
Copyright (C) 2000 - 2006 Intel Corporation
Supports ACPI Specification Revision 3.0a

dsdt_2.6.21.dsl    20:     Name (_T00, 0x00)
Warning  1097 -                     ^ Unknown reserved name (_T00)

dsdt_2.6.21.dsl  6218:             Acquire (MUTE, 0x03E8)
Warning  1103 -   Possible operator timeout is ignored ^

dsdt_2.6.21.dsl  6232:             Acquire (MUTE, 0x03E8)
Warning  1103 -   Possible operator timeout is ignored ^

dsdt_2.6.21.dsl  6247:             Acquire (MUTE, 0x03E8)
Warning  1103 -   Possible operator timeout is ignored ^

dsdt_2.6.21.dsl  6262:             Acquire (MUTE, 0x0FFF)
Warning  1103 -   Possible operator timeout is ignored ^

dsdt_2.6.21.dsl  6276:             Acquire (MUTE, 0x03E8)
Warning  1103 -   Possible operator timeout is ignored ^

dsdt_2.6.21.dsl  6291:             Acquire (MUTE, 0x03E8)
Warning  1103 -   Possible operator timeout is ignored ^

dsdt_2.6.21.dsl  6306:             Acquire (MUTE, 0x03E8)
Warning  1103 -   Possible operator timeout is ignored ^

dsdt_2.6.21.dsl  6504:     Method (WFZF, 1, NotSerialized)
Warning  1086 -                       ^ Not all control paths return a 
value (WFZF)

dsdt_2.6.21.dsl  6519:                 Return (Stall (0x0F))
Error    4094 -                                    ^ syntax error, 
unexpected PARSEOP_STALL

dsdt_2.6.21.dsl  6606:         Zero
Error    4094 -                   ^ syntax error, unexpected PARSEOP_ZERO

dsdt_2.6.21.dsl  6671:         Zero
Error    4094 -                   ^ syntax error, unexpected PARSEOP_ZERO

ASL Input:  dsdt_2.6.21.dsl - 7677 lines, 256431 bytes, 2870 keywords
Compilation complete. 3 Errors, 9 Warnings, 0 Remarks, 701 Optimizations






can you help me to fix the errors?

thanks and bye Markus

  reply	other threads:[~2007-05-01 18:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01  9:40 syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITIONBLOCK Markus Feldmann
2007-05-01 10:08 ` Alexey Starikovskiy
2007-05-01 10:38   ` Markus Feldmann
     [not found]   ` <46371966.2020300@gmx.de>
2007-05-01 13:38     ` Alexey Starikovskiy
2007-05-01 18:43       ` Markus Feldmann [this message]
2007-05-03  6:35       ` Markus Feldmann
2007-05-03 16:12         ` Alexey Starikovskiy
2007-05-04 16:30           ` Markus Feldmann
2007-05-06 13:32           ` Markus Feldmann

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=46378A36.7080108@gmx.de \
    --to=feldmann_markus@gmx.de \
    --cc=aystarik@gmail.com \
    --cc=linux-acpi@vger.kernel.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