iasl
Hi all ..
.. long story, and I shan't bother you with the details ;-)
Is there such a thing as a version of iasl that doesn't depend on glibc 2.3 and will work with glibc 2.2? And, if so, could someone point me in the right direction to download a copy?
Many thanks!
sjb
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only event dedicated to issues related to Linux enterprise solutions www.enterpriselinuxforum.com
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 10 lines · sjb
Hi all ..
.. long story, and I shan't bother you with the details ;-)
Is there such a thing as a version of iasl that doesn't depend on glibc 2.3 and will work with glibc 2.2? And, if so, could someone point me in the right direction to download a copy?
Many thanks!
grab acpica-unix from intel site instead, untar, go to 'compiler' directory, 'make' and hopefully you will get iasl.
I do have trouble with bison version 1.75, but I guess that my bison is broken ? With bison 1.31, all seems to be OK.
Plus, I got some random core dump with the latest one?
Signature · 10 lines
Ducrot Bruno -- Which is worse: ignorance or apathy? -- Don't know. Don't care. ------------------------------------------------------- Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only event dedicated to issues related to Linux enterprise solutions www.enterpriselinuxforum.com
A message that is not in the archive (sent off-list or not yet received): 20030509133703.GH2954-j6u/t2rXLliUoIHC/UFpr9i2O/[email protected]
Quoted 2 lines · Ducrot Bruno
grab acpica-unix from intel site instead, untar, go to 'compiler' directory, 'make' and hopefully you will get iasl.
D'oh! Why didn't I think of that?! *8-)
Quoted 3 lines
I do have trouble with bison version 1.75, but I guess that my bison is broken ? With bison 1.31, all seems to be OK.
Plus, I got some random core dump with the latest one?
Well .. mine compiled cleanly and ..
ottaky@vaio:~/acpi> ./iasl -tc dsdt.asl
Intel ACPI Component Architecture
ASL Optimizing Compiler / AML Disassembler version 20030424 [May 7 2003] Copyright (C) 2000 - 2003 Intel Corporation
Supports ACPI Specification Revision 2.0b
dsdt.asl 529: Field(ECR_, AnyAcc, Lock, Preserve) {
Error 1048 - ^ Host Operation Region requires ByteAcc access
dsdt.asl 1288: Field(PIUC, DWordAcc, Lock, Preserve) {
Error 1047 - ^ Access width is greater than region size
dsdt.asl 2122: If(\_OSI) {
Error 1028 - Too few arguments ^ (\_OSI requires 1)
dsdt.asl 2123: "Windows 2001"
Error 1037 - parse error ^
ASL Input: dsdt.asl - 2157 lines, 75307 bytes, 1552 keywords Compilation complete. 4 Errors, 0 Warnings, 0 Remarks, 381 Optimizations
So, I guess the 1st error is fixable by changing "AnyAcc" for "ByteAcc". Not sure about no.s 2 & 3 ...and WTF is "Windows 2001" doing in there?!
Any DSDT gurus out there? This is from a Sony Vaio U1 BTW.
sjb
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only event dedicated to issues related to Linux enterprise solutions www.enterpriselinuxforum.com
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 16 lines · sjb
Quoted 3 lines · Ducrot Bruno
grab acpica-unix from intel site instead, untar, go to 'compiler' directory,
'make' and hopefully you will get iasl.D'oh! Why didn't I think of that?! *8-)
Quoted 3 lines
I do have trouble with bison version 1.75, but I guess that my bison is broken ? With bison 1.31, all seems to be OK.
Plus, I got some random core dump with the latest one?Well .. mine compiled cleanly and ..
ottaky@vaio:~/acpi> ./iasl -tc dsdt.asl
Quoted 8 lines
Intel ACPI Component Architecture
ASL Optimizing Compiler / AML Disassembler version 20030424 [May 7 2003] Copyright (C) 2000 - 2003 Intel Corporation
Supports ACPI Specification Revision 2.0bdsdt.asl 529:
Field(ECR_, AnyAcc, Lock, Preserve){
Error 1048 - ^ Host Operation Region
requires ByteAcc access
It should be ByteAcc instead of AnyAcc
Quoted 3 lines
dsdt.asl 1288:
Field(PIUC, DWordAcc, Lock, Preserve){
Error 1047 - ^ Access width is greater than
region size
Hard to tell. Need the PIUC definition:
OperationRegion(PIUC, ..., ..., ...)
and all the Field(s) (with their content) which
look like
Field(PIUC, ...) {
...
}
(but if PIUC is a OP defined as a PCI_Config, I would say that it should be ByteAcc, or WordAcc. I doubt that it have to be DWordAcc).
Quoted 6 lines
dsdt.asl 2122:
If(\_OSI){
Error 1028 - Too few arguments ^ (\_OSI requires 1)dsdt.asl 2123: "Windows 2001"
Error 1037 - parse error ^
It should be
If(\_OSI("Windows 2001")) {and you may have to add:
extern (\_OSI)
(but I am not sure if it is OK with latest iasl).
BTW, could you try 'iasl -d mydsdt' in order to disassemble your DSDT, and check if 'If (\_OSI ("Windows 2001"))' is correct ?
Signature · 10 lines
Ducrot Bruno -- Which is worse: ignorance or apathy? -- Don't know. Don't care. ------------------------------------------------------- Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only event dedicated to issues related to Linux enterprise solutions www.enterpriselinuxforum.com
A message that is not in the archive (sent off-list or not yet received): 20030509154224.GK2954-j6u/t2rXLliUoIHC/UFpr9i2O/[email protected]
Quoted 10 lines · Ducrot Bruno
It should be
If(\_OSI("Windows 2001")) {and you may have to add:
extern (\_OSI)
(but I am not sure if it is OK with latest iasl).BTW, could you try 'iasl -d mydsdt' in order to disassemble your DSDT, and check if 'If (\_OSI ("Windows 2001"))' is correct ?
I did and it appears to produce better output than acpidump ...
It decompiled that "Windows 2001" line correctly as
If (\_OSI ("Windows 2001"))
{
Store (0x04, OSTP)
}I fixed the "AnyAcc" error, and now all I see is ..
ottaky@vaio:~/acpi> ./iasl -tc dsdt.dsl
Intel ACPI Component Architecture
ASL Optimizing Compiler / AML Disassembler version 20030424 [May 7 2003] Copyright (C) 2000 - 2003 Intel Corporation
Supports ACPI Specification Revision 2.0b
dsdt.dsl 1902: Field (PIUC, DWordAcc, Lock, Preserve)
Error 1047 - ^ Access width is greater than region size
ASL Input: dsdt.dsl - 3047 lines, 101035 bytes, 1552 keywords
The OperationRegion line reads ..
OperationRegion (PIUC, PCI_Config, 0x74, 0x01)
Does that provide enough info?
Thanks for helping out BTW *8-)
sjb
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only event dedicated to issues related to Linux enterprise solutions www.enterpriselinuxforum.com