public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Martijn Pieters <mj-a5Jd59zECFiB+jHODAdFcQ@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ASL fixing questions
Date: Fri, 13 Feb 2004 09:20:29 -0500	[thread overview]
Message-ID: <402CDD2D.9050808@zopatista.com> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401CBB6AE-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>

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

Yu, Luming wrote:
>>Okay, so I have a nice new eMachines M6805, but ACPI support 
>>is screwed. 
> 
> 
> I want to know the error messages that give you impression that
> ACPI support is screwed. Or some expected functionality has 
> broken.  It's very important to judge whether we need to hack 
> ASL , and give you a hint to hack which part of ASL.

Just starting on my ACPI journey. My first tries to get an ACPI kernel 
working have led to a plethora of probems, and at the time I didn't have 
enough experience to be able to seperate ACPI problems from others.

I'll get back to those problems later, if/when I have time (next 3-5 
weeks are going to be absolutely more than hecktic, I am moving across 
the Atlantic again).

>>I am trying fix the AML the bios provided me, and iron out all the 
>>errors and warnings. Attached my DSDT.dsl, as fixed so far.
>>
>>So far I got rid of the warnings (_WAK didn't return anything; fixed 
>>with examples from working DSTS-es, _BTS method didn't return 
>>anything 
>>on some control paths; move return out of if statement down).
> 
> 
> I'm not sure this kind of hack could solve the problem you have.

No, but they were a start. I am hopeful that the Field error encountered 
may have something to do with it. But again, I have no time right now to 
experiment and find out. This laptop has got a job to do right now.

Martijn

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  parent reply	other threads:[~2004-02-13 14:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13  3:43 ASL fixing questions Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB6AE-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-13 14:20   ` Martijn Pieters [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-13  4:08 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB6AF-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-13  4:40   ` Bruno Ducrot
     [not found]     ` <20040213044014.GG13262-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-21 17:15       ` Pavel Machek
2004-02-12  3:58 Martijn Pieters
     [not found] ` <402AF9FF.3020706-a5Jd59zECFiB+jHODAdFcQ@public.gmane.org>
2004-02-12  4:48   ` Martijn Pieters
2004-02-12  6:45   ` Martijn Pieters
2004-02-12  9:37   ` Bruno Ducrot
     [not found]     ` <20040212093732.GP13262-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-12 14:52       ` Martijn Pieters
     [not found]         ` <402B9313.9000701-a5Jd59zECFiB+jHODAdFcQ@public.gmane.org>
2004-02-12 16:33           ` Martijn Pieters
     [not found]             ` <402BAABC.5040706-a5Jd59zECFiB+jHODAdFcQ@public.gmane.org>
2004-02-12 17:24               ` Martijn Pieters
2004-02-12 20:43               ` Bruno Ducrot
     [not found]                 ` <20040212204335.GU13262-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-12 20:56                   ` Martijn Pieters
     [not found]                     ` <402BE889.5090502-a5Jd59zECFiB+jHODAdFcQ@public.gmane.org>
2004-02-12 21:18                       ` Bruno Ducrot
     [not found]                         ` <20040212211803.GW13262-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-12 21:25                           ` Martijn Pieters
     [not found]                             ` <402BEF3A.3080702-a5Jd59zECFiB+jHODAdFcQ@public.gmane.org>
2004-02-13  2:00                               ` Martijn Pieters
2004-02-12 21:20                       ` Martijn Pieters
     [not found]                         ` <402BEE34.9050908-a5Jd59zECFiB+jHODAdFcQ@public.gmane.org>
2004-02-12 21:26                           ` Bruno Ducrot
     [not found]                             ` <20040212212649.GX13262-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-12 21:35                               ` Martijn Pieters
     [not found]                                 ` <402BF19C.9050803-a5Jd59zECFiB+jHODAdFcQ@public.gmane.org>
2004-02-12 22:06                                   ` Bruno Ducrot
     [not found]     ` <402B7917.2090505@zopatista.com>
     [not found]       ` <402B7917.2090505-a5Jd59zECFiB+jHODAdFcQ@public.gmane.org>
2004-02-12 21:16         ` Bruno Ducrot
     [not found]           ` <20040212211615.GV13262-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-12 21:34             ` Martijn Pieters
     [not found]               ` <402BF14A.8040406-a5Jd59zECFiB+jHODAdFcQ@public.gmane.org>
2004-02-12 22:11                 ` Bruno Ducrot
     [not found]                   ` <20040212221108.GZ13262-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-12 23:35                     ` Martijn Pieters

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=402CDD2D.9050808@zopatista.com \
    --to=mj-a5jd59zecfib+jhodadfcq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@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