Hi Michael, On 20 Jan, this message from Michael Hanselmann echoed through cyberspace: > Okay, so you don't have a keyboard the patch/driver doesn't know about.
No, I also verified the USB ids vs. your patch. >> In default config, Fn+Fx (eg. Fn+F1) do produce different keycodes. >> But it seems the Fn-ified keycode is not what it should be. > > Fn sends KEY_FN, too. The sequences you should get: Are you sure the patch I'm using already does that? I use the older one (patchwork.ozlabs.org/linuxppc/patch?id=3856). > pb_fnmode=1, F1: > KEY_BRIGHTNESSDOWN down, KEY_BRIGHTNESSDOWN up I never get these alone, whatever I do. > pb_fnmode=1, Fn+F1: > KEY_FN down, KEY_F1 down, KEY_F1 up, KEY_FN up What is the KEY_FN code? 0x1d0? > pb_fnmode=2, F1: > KEY_F1 down, KEY_F1 up > > pb_fnmode=2, Fn+F1: > KEY_FN down, KEY_BRIGHTNESSDOWN down, KEY_BRIGHTNESSDOWN up, KEY_FN up > > See linux/include/linux/input.h for the constants. In the Fn+ cases, > the latter two events might be swapped, depending on in which order > you release the keys. pb_fnmode=1 is the default, known as fkeysfirst > in pbbuttonsd or also as the Mac OS X default mode. What is the difference between key-down and key-up? I thought the highest bit is set; but what about multi-byte sequences or keycodes above 127? > I hope this information brought you some steps further. Not yet, but thanks anyway :-) Cheers Michel ------------------------------------------------------------------------- Michel Lanners | " Read Philosophy. Study Art. 23, Rue Paul Henkes | Ask Questions. Make Mistakes. L-1710 Luxembourg | email [EMAIL PROTECTED] | http://www.cpu.lu/~mlan | Learn Always. " -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]