07/02/08 01:15, Len Brown wrote/a écrit: > On Sunday 03 February 2008 12:28, Éric Piel wrote: >> Hello, >> >> Here are three patches to implement the override of DSDT via initramfs. >> I haven't included the feature for overriding the SSDTs as it's seems >> it's still a bit controversial, and anyway for now there is very little >> need for it. It should be fairly trivial to add it later if need arises. >> >> The patches are against 2.6.24-git-du-jour, and they have been >> boot-tested on my laptop. > > Thanks Eric, > I'll take Thomas, Carlos and my comments and my comments > and try to address them w/ a follow-up patch tonight. > > -Len Ah, Great! Just for info, I had started answering the comments from Thomas and Carlos. Here is my proposed version as description for Kconfig: With this feature you will be able to provide a customized DSDT by adding it to your initramfs. Overriding of the DSDT is mainly thought for developing/testing purposes! If you have problems with ACPI on your machine and you have fixed it up by modifying the DSDT, do not override the DSDT as a long term solution. E.g. if you add new memory to your machine, the modified DSDT will not work (BIOS would generate a slightly adjusted one). Always report bugs in a DSDT to your computer vendor and to bugzilla.kernel.org (assigned to the ACPI component). In case your mkinitrd tool does not support this feature, a script is provided in the documentation. For more details on this option see <file:Documentation/dsdt-initrd.txt>. If you feel like tinkering with the DSDT or might have to test a corrected DSDT one day select this option. It is safe to say Y here. You can use it as inspiration ;-) More over, I was thinking of adding a note in dsdt-initrd.txt like this: Do note that the format of the table included in the initramfs is binary (iasl -ta), while if you include the DSDT straight inside the kernel, the format is hexadecimal (iasl -tc). See you, Eric - 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