On Sun, Mar 22, 2009 at 11:14:49PM +0000, Matthew Garrett wrote: > On Mon, Mar 23, 2009 at 08:10:30AM +0900, Mattia Dongili wrote: > > On Sun, Mar 22, 2009 at 10:46:52PM +0000, Matthew Garrett wrote: > > > Ok, sounds like the mapping needs to be changed. Can you let me know > > > which ACPI events are generated for each key? > > > > Yes it does. > > A vaio SR user sent me this list for 0x9c that after a call to SN07(202) > > becomes: > > 0x9c as well? Interesting. Easy enough to generalise that code, I guess. well, I was thinking of a two layer lookup keyed on the event code (0x9[02ce]). > If we don't have a match, maybe we should just send the scancode with > KEY_UNKNOWN and let hal remap them? the problem is that the decoded keypress (after the SN07 call) generates duplicates, i.e.: 0x81 is fn+f1 for the 0x92 case and some "Mode" key for 0x9c the an SR model. I guess sending the whole combination as the scancode would do the trick (0x9c81). But as long as we can make it consistent with what sony-laptop currently sends to userspace then we should try to have a map. -- mattia :wq! -- 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
