From: Martijn Pieters <mj-a5Jd59zECFiB+jHODAdFcQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ASL fixing questions
Date: Thu, 12 Feb 2004 11:33:00 -0500 [thread overview]
Message-ID: <402BAABC.5040706@zopatista.com> (raw)
In-Reply-To: <402B9313.9000701-a5Jd59zECFiB+jHODAdFcQ@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 994 bytes --]
>> Do you have a SSDT table ? If so, this object may be in that SSDT
>> instead.
> SSDT decompilation fails with:
>
> dswload-0264: *** Error: Looking up [\_PR_.CPU0] in namespace,
> AE_NOT_FOUND
> psparse-1283: *** Error: [NULL NAME], AE_NOT_FOUND
> Could not parse ACPI tables, AE_NOT_FOUND
>
> How can I decompile the SSDT table with the DSDT namespace available? Ue
> an Include in the DSDT AML? Your suspicion could be right, hexedit of
> the SSDT code does show a _PPC declaration.
Okay, I decompiled the SSDT table by hand (small table anyway), find it
attached (really!). It doates indeed define the _PPC field and two other
names, which make little sense to me.
Which leads to my next question: I thought leading underscore names were
reserved by the ACPI spec. ACPI 1.0 doesn't define the names, and ACPI
2.0 defines them differently. Can this lead to problems with the Linux
ACPI implementation making assumptions about ACPI 1.0 code with 2.0
extensions?
Martijn
[-- Attachment #1.2: ssdt.dsl --]
[-- Type: text/x-dsl, Size: 1305 bytes --]
DefinitionBlock ("SSDT.aml", "SSDT", 1, "PTLTD ", "POWERNOW", 100925440)
{
Scope (\_PR.CPU0)
{
Name (_PCT, Package (0x02)
{
Buffer (0x11)
{
0x82, 0x0C, 0x00, 0x7F, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x79, 0x00
},
Buffer (0x11)
{
0x82, 0x0C, 0x00, 0x7F, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x79, 0x00
}
})
Name (_PSS, Package (0x03) // 102 (206)
{
Package (0x06)
{
0x08070000,
0xB36A0000,
0x7D000000,
0x09000000,
0x8A2920E0,
0x8A010000
},
Package (0x06)
{
0x40060000,
0xA8610000,
0x7D000000,
0x09000000,
0xBB2A20E0,
0xBBC20000
},
Package (0x06)
{
0x20030000,
0x7F3C0000,
0x7D000000,
0x09000000,
0x002E20E0,
0x00060000
}
})
Name (_PPC, 0x00)
}
}
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-02-12 16:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 3:58 ASL fixing questions 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 [this message]
[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
-- strict thread matches above, loose matches on Subject: below --
2004-02-13 3:43 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB6AE-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-13 14:20 ` Martijn Pieters
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
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=402BAABC.5040706@zopatista.com \
--to=mj-a5jd59zecfib+jhodadfcq@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