On Fri, Mar 23, 2012 at 6:26 PM, Thomas Renninger <trenn@xxxxxxx> wrote: >> maybe could have dmi checking for more strict checking. > I do not understand what should get checked? > Hm, I guess you mean if a general table is always added that is distributed > on different platforms and you want to white/blacklist machines to > explicitly load/not load the table? > This must not happen. > The tables are always platform specific and you provide tables for > a specific machine only for debugging purposes. > >> also would help if have one boot command that could skip overriding. > Same. Both should not be needed. > > Or you have a use-case in mind I cannot not think of... For known broken system, could be old, or vendor does not want to provide updated firmware anymore. if the user could boot system with debug parameter like "noapic maxcpus=1...." then have user space util to extract acpi tables, and patch them and repack them into initrd. next boot will have system running with optimal ... If we could do that, we could avoid or kill workaround and quirks in the kernel. So we may need some strict check or skip when you are moving disk around or update different bios later. Thanks Yinghai -- 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
