> > 1. In /proc/acpi/events few keys which looks normal in DSDT are not > > reported. I found that all of them have code bigger than 0x80. I founded > > those lines and changed them to return codes below 0x80 (to ones that > > are not used) and that solved problem. I did not have time to look into > > acpi source code and maybe my solution is not the best way to do it, and > > maybe not solves the problem, but works for me. > > Example: > > > > - F2 wifi button > > //Notify (\_SB.ATKD, 0x88) > > Notify (\_SB.ATKD, 0x56) > > > > The only exception is sleep button F1 but it is notified not to > > \_SB.ATKD but to \_SB.SLPB and is processed by buttons module. > > > > Notify (\_SB.SLPB, 0x80) > > > > Is it a bug or a feature that codes over 0x80 are not reported? > I don't know :/ So, let's ask linux-acpi@xxxxxxxxxxxxxxx According to the ACPI spec, section 5.6.3 "Device Object Notifications" 0-7f common for all devices 80-bf device specific c0-ff vendor specific so I think that what happens to codes of 80 and above should depend on the device driver that is bound to the device that handles the notify. I'll venture that SLPB is the sleep button, and the standard button driver is already bound to handle that one. -Len - 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
