Looking at this, it seems that the affected machines have AMW0_GUID1 but none of the WMID GUIDs. By the looks of things this is just a semi-standardised way to trigger an SMM trap and communicate with the firmware. This makes things tricker to track down (because once we're in SMM we have no way of knowing what the firwmare's doing), but potentially there's some method to identify the machine here. Carlos, do we have any idea what the inputs and outputs for this method mean other than what's in AMW0_set_capabilities()? -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
