On Sat, Mar 21, 2009 at 02:55:02PM +0000, Matthew Garrett wrote: > 0x33: 0x34: 0x36: 0x37: > 0, 0x0101 0x0101 0x0101 0x0101 > 1, 0x0102 0x0102 0x0102 0x0102 > 2, 0x0100 0x0100 0x0100 0x0100 > 3, 0x0104 0x0104 > 4, 0x0107 0x010F 0x0107 0x010F > 5, 0x0106 0x0106 > 6, 0x0000 0x0113 > 7, 0x0111 0x010A > C, 0x010C > D, 0x010D 0x010D > E, 0x0105 0x0105 0x0105 0x0105 > F, 0x0103 0x0103 0x0103 Actually slightly more complicated than that - some are only stored on certain OS versions. Here's a more complete table. 0x33: 0x34: 0x36: 0x37: 0, 0x0101 0x0101 0x0101 0x0101 1, 0x0102 0x0102 0x0102 0x0102 2, 0x0100 0x0100 0x0100 0x0100 3, 0x0104 0x0113 0x0104 4, 0x0107 0x010F 0x0107 0x010F 5, 0x0106 0x0106 6, 0x0113 0x0113 7, 0x0111 0x010A C, 0x010C D, 0x010D 0x010D E, 0x0105 0x0105 0x0105 0x0105 F, 0x0103 0x0103 0x0103 The way that 0x113 moves around leaves me pretty sure that calling SN07 without checking what the function signature is is not a good idea. I'll rewrite my patch. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- 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
