On Wed, 12 Mar 2008, Lukas Hejtmanek wrote: > On Wed, Mar 12, 2008 at 10:35:29AM -0300, Henrique de Moraes Holschuh wrote: > > You shouldn't need to do anything other than teach userspace to respond to > > them, as they generate the proper KEY_* events. If you are giving the AML > > _OSI(Linux), at least... > > > > But maybe looking at the keyboard output in console mode, to make triple > > sure the events ARE being sent over the KDC as they should, would be in > > order? > > so, do I understand correctly that volume keys have been controlled by ACPI > and seemed to work independently on SW and now (exactly since when?) are > passed complety to the user space as key codes? Yes, since the first *61 model. And field-upgradeable firmware revisons have a say on how this thing works, since the entire KDC is software in a Lenovo ThinkPad (it is just a small part of the EC firmware, that comes with the BIOS upgrades). I have some long email sitting on my draft folders about how to restore full sanity to thinkpad mixer behaviour on Linux, but I have to cool down for a few days before I revise it and send it. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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
