On Wednesday, February 11, 2015 01:43:06 AM Matthew Garrett wrote: > On Wed, Feb 11, 2015 at 02:57:48AM +0100, Rafael J. Wysocki wrote: > > > Well, it looks like we circled back to http://marc.info/?l=linux-acpi&m=142361557824868&w=4 :-) > > Right. And, like I said, if there's a "We're seeing increased power > consumption" bug then there's an incentive for people from Intel to > actually help identify the root source, whereas if there's a "We can't > enable Thunderbolt hotplug on this platform Intel pretend has nothing to > do with them because otherwise we'll see increased power consumption", > it's going to be so far down people's list of priorities that it's > probably not going to happen. And you said that already too, so I guess we can circle like that forever. Only one more comment: In order to "identify the root cause" it is pretty much necessary to know what _OSI("Darwin") causes the firmware to actually do and the only party knowing that is Apple. The only question I can ask hardware people is what it *theoretically* may be doing to trigger the observed behavior and honestly I doubt I'll get a useful answer to that. -- 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
