Re: [PATCH] Console keyboard events and accessibility

[Jan Engelhardt]

On Aug 21 2007 02:57, Samuel Thibault wrote:
>
>Some external modules like Speakup need to use the PC keyboard to control
>them and also need to get keyboard feedback (caps lock status, etc.)
>
>This adds a keyboard notifier that such modules can use to get the keyboard
>events and possibly eat them, at several stages:
>
>- keycodes: even before translation into keysym.

They can use the raw xlation for that. The "showkeys" utility and Xorg are
likely to do that. (In fact, there is a helping sysrq called Unraw in case
there are problems.)

>- unbound keycodes: when no keysym is bound.
>- unicode: when the keycode would get translated into a unicode character.
>- keysym: when the keycode would get translated into a keysym.
>- post_keysym: after the keysym got interpreted, so as to see the result
>  (caps lock, etc.)

For all these, I think new xlats should be added that have the desired
behavior.

>+	int shift;		/* Current shift mask */
>+	unsigned int value;	/* keycode, unicode value or keysym */
>+};
>+
>+extern int register_keyboard_notifier(struct notifier_block *nb);
>+extern int unregister_keyboard_notifier(struct notifier_block *nb);
> #endif
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/