On Wednesday, October 20, 2010 10:28:06 am Stefan Assmann wrote: > Let me take a look at the current situation and see if I can come up > with a solution. Sorry if things got messy. When you redo this, can you update the printks to use dev_info() and "[%04x:%04x]" for vendor/device, like the rest of PCI? Actually, the bridge_has_boot_interrupt_variant() printk looks superfluous to me. Do you know how Windows handles these machines? I'm just wondering if there's some ACPI or other information from the BIOS that we're not handling quite correctly, and if we fixed that maybe we wouldn't need a quirk. ISTR a paper or some kind of writeup you did, but the commit (e1d3a90846) doesn't mention it. Am I mis-remembering that? It'd be kind of nice for archaeologists like me if there were a kernel bugzilla with before/after dmesg logs and stuff. Bjorn -- 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
