I demand that Matthew Garrett may or may not have written... > On Tue, Feb 24, 2009 at 03:29:36PM +0000, Darren Salt wrote: >> Not HOTPLUG_PCI_PCIE? > No - it just depends on the hotplug PCI core. >> With that selected (I see no point in testing this otherwise) *and* >> pciehp_force=1, I get -EBUSY when the hotplug slot registration is >> attempted and no wireless, bluetooth or hot key reporting; wireless & >> bluetooth are switched off at that point (I made sure that they were >> enabled via BIOS setup). Without that option, all is fine. > Right, so that sounds like everything works as expected. I guess to avoid > breaking existing setups we should probably be a bit nicer there. Can you > test whether this one works? Works fine, AFAICS. If that's what's to be committed, then: Tested-By: Darren Salt <linux@xxxxxxxxxxxxxxxxxxxxxxxxxxx> [snip] -- | Darren Salt | linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Burn less waste. Use less packaging. Waste less. USE FEWER RESOURCES. Beware of quantum ducks. Quark! Quark! -- 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
