Re: ASL fixing questions

Martijn Pieters
2004-02-12T14:52:03Z

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

(Resend to all, corrected address, sorry Bruno,
one-hand-typing-with-baby-error, she's-asleep-and-so-am-I-failure)

Bruno Ducrot wrote:
>>dsdt.dsl 2035: Store (Zero, \_PR.CPU0._PPC)
>>Error 1022 - Object does not exist ^ (\_PR.CPU0._PPC)
>
>
> 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.

> Well, actually there is a lot of AML's that claims to be only 1.0
> compliant but have a lot of 2.0 extensions...

Hmmm,but _PPC is a AML 2.0 method to query possible states, not a field
to set the state, such as this code does.

>>dsdt.dsl 2953: PWST, 2,
>>Error 1051 - ^ Access width of Field Unit extends beyond region limit
>
>
> You can fix it by compiling the kernel with CONFIG_ACPI_RELAX option.
> I will read your the ASL, though, to be sure.

Okay, the email with the ASL attached to the list was released by the
moderators already.

>>Last but not least, tehre is one Field declaration that wants to define
>>AnyAcc to a OperationRegion, something that apparently isn't possible:
>>
>>dsdt.dsl 3235: Field (ERAM, AnyAcc, NoLock, Preserve)
>>Error 1048 - ^ Host Operation Region requires ByteAcc access
>
> > s/AnyAcc/ByteAcc on the faulty line, perhaps ;)

There are two Field definitions referring to that OperationRegion; one
ByteAcc and one AnyAcc. It is clear the author expected this to work and
needed the behaviour..