public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Asus K8V Delux broken acpi tables?
Date: Mon, 10 Oct 2005 22:36:12 -0400	[thread overview]
Message-ID: <434B251C.3090300@cfl.rr.com> (raw)
In-Reply-To: <434B171A.3040103-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>

I got iasl -d to disassemble /proc/acpi/dsdt, and your patch cleanly 
applied to that.  When I try to recompile the patched file, I get these 
errors though:

dsdt.dsl    54:             Store (0xAA, DBG8)
Error    1061 -       Object does not exist ^  (DBG8)

dsdt.dsl    58:             Store (0xAC, DBG8)
Error    1061 -       Object does not exist ^  (DBG8)

dsdt.dsl    65:     Method (OSFL, 0, NotSerialized)
Warning  2085 -                ^ Not all control paths return a value (OSFL)

dsdt.dsl    74:             Store (0xAC, DBG8)
Error    1061 -       Object does not exist ^  (DBG8)

dsdt.dsl    78:         If (MCTH (\_OS, "Microsoft Windows NT"))
Error    1094 -                      ^ syntax error, unexpected 
PARSEOP_NAMESEG, expecting ')'

dsdt.dsl    82:         Else
Error    1094 -            ^ syntax error, unexpected PARSEOP_ELSE

dsdt.dsl    84:             If (MCTH (\_OS, "Microsoft WindowsME: 
Millennium Edition"))
Error    1094 -                          ^ syntax error, unexpected 
PARSEOP_NAMESEG, expecting ')'
dsdt.dsl    88:         }
Error    1094 -         ^ syntax error, unexpected '}', expecting $end

Any ideas?


Phillip Susi wrote:

> I think I updated my bios a month or two ago.  I'm not quite sure how 
> to recompile my DSDT.  I thought I needed to use iasl to decompile the 
> existing DSDT from acpidump, then apply your patch, then recompile.  I 
> seem to be missing something though, iasl -d doesn't seem to like my 
> acpidump.log.
> Also getting iasl compiled was kind of a pain, the code is a bit 
> borked.  First I had to add the -l flag to flex so that unput() could 
> be used correctly, then the code was declaring a variable in one place 
> as a char [] and in another as a char *, so I had to fix that to get 
> it to compile.  Even then it had a bunch of warnings because of 
> incorrect casts due to assumptions about being on a 32bit architecture 
> ( I'm running 64 bit ).
>


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

  parent reply	other threads:[~2005-10-11  2:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-08  5:44 Asus K8V Delux broken acpi tables? Phillip Susi
     [not found] ` <43475CDB.6070204-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2005-10-08 16:02   ` Phillip Susi
     [not found]     ` <4347ED97.1090504-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2005-10-10 10:00       ` Thomas Renninger
     [not found]         ` <434A3BB4.1050404-l3A5Bk7waGM@public.gmane.org>
2005-10-11  1:36           ` Phillip Susi
     [not found]             ` <434B171A.3040103-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2005-10-11  2:36               ` Phillip Susi [this message]
2005-10-11  7:32               ` Thomas Renninger
2005-10-12 11:37   ` Stefan Seyfried

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=434B251C.3090300@cfl.rr.com \
    --to=psusi-3tlf1voikjtqt0dzr+alfa@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