Heya, My Dell laptop has a good bunch of keys that show this behaviour: Apr 25 11:23:10 snoogens kernel: atkbd.c: Unknown key pressed (translated set 2, code 0x87 on isa0060/serio0). Apr 25 11:23:10 snoogens kernel: atkbd.c: Use 'setkeycodes e007 <keycode>' to make it known.
Given that all Dell laptops generate this kind of behaviour, that all the keys match on all the models (I know about), would it be possible/sane to add some code to the AT keyboard driver to handle those keys when the DMI matches? I can think of a number of reasons why it would be a bad idea: - overly complicated driver that handles a lot of "broken" hardware cases - slippery-slope (next it's for IBM/Sony/whatever laptops/keyboards, etc.) But I'd rather have this done completely in kernel space, where it belongs (after all, that's the point of drivers to handle hardware through common interfaces). Any comments, ideas on how to do this as cleanly and unobtrusively? Cheers -- Bastien Nocera <[EMAIL PROTECTED]>
