On Friday, January 18, 2013 09:50:59 AM Yinghai Lu wrote: > On Fri, Jan 18, 2013 at 9:35 AM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote: > > If you want "pci=nopciehp" as a way for users to deal with this > > problem by forcing the use of acpiphp, I object. Windows manages to > > make these slots work without having users do anything special, so we > > should be able to do it, too. > > Agreed. > > We need to think that more. > > I think that we should fix acpiphp, and should follow first come and > first serve for acpiphp and pciehp. That would introduce regressions for some users, though. I actually think we should merge acpiphp with pciehp and make one driver that can use both types of signalling. There would be a problem with getting notifications for the same event from both sources, but that doesn't seem to be unsolvable. And I don't think that that one combined driver should be modular. Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
