Comment 11 for bug 751471

Thanks Jerone for the explanation, I understand better the situation now, also I looked again at bug 408903. The kernel support for the key here should be simple, once upstream agrees on a new key code, and thinkpad_acpi needs handling to report it (not in udev), as from what I see in the reports in both bugs it is an hotkey handled by acpi->thinkpad_acpi (it's sending KEY_UNKNOWN, and I was in fact expecting keymap to report this for thinkpad_acpi hotkeys, but don't know/remember now if it reports unknown key).

Something like the kernel I uploaded at http://people.canonical.com/~herton/thinkpad_micmute/ (patches there too)

I didn't look at the led support, but can you and Marc check this kernel and see if it's ok? (properly reporting new key code 0x21b). Also I placed some debugging just to check everything is ok, please attach dmesg after pressing the mic mute key.

Also note this is the first part, only the mute key is properly reported, but will need sound mixer app (user space support) to get the new key code and mute the mic in the sound mixer.

If this first part is ok, I'll rise the issue upstream and propose the new key code.