public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <mail-smMupaH/RwJM7kwft8N7nw@public.gmane.org>
To: mrfree-97W46K3QqA41GQ1Ptb7lUw@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Problem fixing DSDT (parse error)
Date: Mon, 06 Dec 2004 16:07:06 +0100	[thread overview]
Message-ID: <41B4759A.7080705@renninger.de> (raw)
In-Reply-To: <41AC9BD8.9050604-smMupaH/RwJM7kwft8N7nw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]

Ok, here it is.
It compiles, but I wouldn't trust this DSDT too much:

e.g.:
1)

If (Local0)
{
      Return (0x1F)
      Store (0x1F, P378)
}
Else
{
      Return (0x0F)
      Store (0x0F, P378)
}
dsdt.dsl.orig  2468:                      Store (0x1F, P378)
Warning  2079 -                           Statement is unreachable ^

dsdt.dsl.orig  2473:                      Store (0x0F, P378)
Warning  2079 -                           Statement is unreachable

Of course the Store method is never reached (I switched the statements, 
don't know exactly what is stored, but it has something to do with the 
battery status ... (insertion/ejection _STA))

2)

Scope (\_SB) is defined about three times.
The compiler seems to accept this, but it's quite confusing.

I just put the IF statements that layed around in the _SB scope into the 
_INI method of _SB. That at leasts avoid the compiler errors and you 
could have a closer look to that what really matters to you.

3)

There is one warning, I don't know about. You can avoid it by compiling 
without optimzation (-oa):
dsdt.dsl.orig  2683:                 Scope (\_SB.PCI0)
Warning  2031 -             Internal compiler error ^  (Not using 
optimized name - did not find node)

      Thomas

P.S: Is it possible that you edited the file in windows, I had to delete 
the \r at the end of each line...

[-- Attachment #2: dsdt.dsl.bz2 --]
[-- Type: application/x-bzip2, Size: 8525 bytes --]

  parent reply	other threads:[~2004-12-06 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30 11:50 Problem fixing DSDT (parse error) mrfree-97W46K3QqA41GQ1Ptb7lUw
     [not found] ` <web-25326080-97W46K3QqA41GQ1Ptb7lUw@public.gmane.org>
2004-11-30 16:12   ` Thomas Renninger
     [not found]     ` <41AC9BD8.9050604-smMupaH/RwJM7kwft8N7nw@public.gmane.org>
2004-12-06 15:07       ` Thomas Renninger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-01  8:53 mrfree-97W46K3QqA41GQ1Ptb7lUw

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=41B4759A.7080705@renninger.de \
    --to=mail-smmupah/rwjm7kwft8n7nw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=mrfree-97W46K3QqA41GQ1Ptb7lUw@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