>On Thu, Aug 03, 2006 at 10:25:43PM +0200, Adrian Bunk wrote: >> ACPI_CUSTOM_DSDT seems to be the most interesting case. >> It's anyway not usable for distribution kernels, and AFAIR the ACPI >> people prefer to get the kernel working with all original DSDTs >> (which usually work with at least one other OS) than letting >> the people workaround the problem by using a custom DSDT. > >Not true at all. For SuSE kernels, we have a patch that lets people >load a new DSDT from initramfs due to broken machines requiring a >replacement in order to work properly. CONFIG_ACPI_CUSTOM_DSDT allows hackers to debug their system by building a modified DSDT into the kernel to over-ride what came with the system. It would make no sense for a distro to use it, unless the distro were shipping only on 1 model machine. This technique is necessary for debugging, but makes no sense for production. The initramfs method shipped by SuSE is more flexible, allowing the hacker to stick the DSDT image in the initrd and use it without re-compiling the kernel. I have refused to accept the initrd patch into Linux many times, and always will. I've advised SuSE many times that they should not be shipping it, as it means that their supported OS is running on modified firmware -- which, by definition, they can not support. Indeed, one could view this method as couter-productive to the evolution of Linux -- since it is our stated goal to run on the same machines that Windows runs on -- without requiring customers to modify those machines to run Linux. -Len - 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
