Most of the problems seen in the SSDT are related to the fact that the disassembler cannot always correctly disassemble code that contains calls to control methods that are external to the table. There is not enough information to disassemble correctly, and the table often needs to be repaired by hand. >-----Original Message----- >From: linux-acpi-owner@xxxxxxxxxxxxxxx [mailto:linux-acpi- >owner@xxxxxxxxxxxxxxx] On Behalf Of Frans Pop >Sent: Thursday, September 25, 2008 9:52 PM >To: Zhao, Yakui >Cc: linux-acpi@xxxxxxxxxxxxxxx >Subject: Re: Syntax errors in SSDT1 table of HP 2510p laptop > >On Friday 26 September 2008, Zhao Yakui wrote: >> Will you please try the latest kernel (2.6.27-rc6) and see whether the >> problem still exists? > >Sorry that I did not make that clear, but I am already running with >current git (v2.6.27-rc7-94-gc0f4d6d). > >> It seems that the problem is fixed by the following commit: >> commit 48feb3c419508487becfb9ea3afcc54c3eac6d80 > >The kernel errors listed in that commit log are rather different from what >I'm seeing. > >Also, how could a commit in the kernel fix a broken ACPI table? No change >in the kernel can repair syntax errors that show up when you disassemble >and recompile the ACPI table itself, can it? >I thought using iasl as I did was the accepted way to uncover errors in a >system's ACPI tables. > >I really think the problem is in the ACPI table in this case, not in the >kernel. > >Cheers, >FJP >-- >To unsubscribe from this list: send the line "unsubscribe linux-acpi" in >the body of a message to majordomo@xxxxxxxxxxxxxxx >More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
