>> Also, it would be great to preserve key up and key down informations >> (sparse keymap have an "autorelease" parameter to control that). > > Okay, I'll add some special casing for this key to support that. You may have to add an optional callback for that in asus-wmi's driver model because it's used by both asus-nb-wmi and eeepc-wmi, and we only want this behavior for eeepc-wmi. > Do you suggest ignoring the 0xea scan codes? Yep, 0xea means "The key is still pressed", but it's useless if we already repport key down and key up events correctly. You'll have to ignore this scan code explicitly to remove traces in dmesg (use KEY_IGNORE). -- Corentin Chary http://xf.iksaif.net -- 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
