On Friday 01 February 2008 04:53, Thomas Renninger wrote: > > That gives you complete and total control over what AML gets run > I doubt that. You said there can be any number of SSDTs. If you know > what you are doing..., but how do you explain someone in a bug that he > has to collect all SSDTs (some via acpidump --addr xy) open an editor, > paste them into the DSDT and so on... Dynamic SSDT's are loaded from OpRegions by address. If you want to change the AML in those opregions, you have to acquire it with acpidump --addr xy. That is true no mater what override scheme you're using. However, if you don't want to modify the dynamic SSDT, then it does not have to be dumped -- it will continue to be accessed via Load() of the opregion; and it is totally unrelated to a DSDT or a DSDT+static-SSDT override. I am doubtful that SSDT override support past what we have already justifies its own complexity. -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
