Comments on: Linux input model http://blogs.gnome.org/hughsie/2008/07/04/linux-input-model/ Blog about geeky stuff Sun, 22 Nov 2009 00:10:33 +0000 http://wordpress.org/?v=2.8.6 hourly 1 By: Rhod http://blogs.gnome.org/hughsie/2008/07/04/linux-input-model/comment-page-1/#comment-520 Rhod Wed, 09 Jul 2008 21:10:17 +0000 http://blogs.gnome.org/hughsie/2008/07/04/linux-input-model/#comment-520 no :p no :p

]]> By: luc http://blogs.gnome.org/hughsie/2008/07/04/linux-input-model/comment-page-1/#comment-508 luc Sat, 05 Jul 2008 20:51:46 +0000 http://blogs.gnome.org/hughsie/2008/07/04/linux-input-model/#comment-508 Great diagram! I looked at key events (and their way from the drawing on the key cap, until the character on the screen) a few years ago, and ended up with a similar diagram on my notebook. Here are just a few details out of my notes (which may be outdated, and possibly wrong anyway!): The key event (press/release) generates up to 6 scancodes. The kernel keyboard driver has two (exclusive?) modes: scancode mode and keycode mode. Scancodes are translated (keymap) into either a character "a", a string "\e[4", an action. Finally if you live out of ascii, you add locales, encodings, and fonts, and you get the complete mess. Great diagram!

I looked at key events (and their way from the drawing on the key cap, until the character on the screen) a few years ago, and ended up with a similar diagram on my notebook. Here are just a few details out of my notes (which may be outdated, and possibly wrong anyway!):
The key event (press/release) generates up to 6 scancodes.
The kernel keyboard driver has two (exclusive?) modes: scancode mode and keycode mode.
Scancodes are translated (keymap) into either a character “a”, a string “\e[4″, an action.
Finally if you live out of ascii, you add locales, encodings, and fonts, and you get the complete mess.

]]> By: Dan http://blogs.gnome.org/hughsie/2008/07/04/linux-input-model/comment-page-1/#comment-506 Dan Sat, 05 Jul 2008 03:10:31 +0000 http://blogs.gnome.org/hughsie/2008/07/04/linux-input-model/#comment-506 I think it is a great learning tool, and that we need a simple image such as this one for each user-visible model. It may be quicker to understand it if it were spread out a bit, and aligned into stacks to make the flow clearer. I think it is a great learning tool, and that we need a simple image such as this one for each user-visible model.

It may be quicker to understand it if it were spread out a bit, and aligned into stacks to make the flow clearer.

]]> By: Andreas http://blogs.gnome.org/hughsie/2008/07/04/linux-input-model/comment-page-1/#comment-502 Andreas Fri, 04 Jul 2008 22:37:48 +0000 http://blogs.gnome.org/hughsie/2008/07/04/linux-input-model/#comment-502 eald, just use xmodmap, saves you a lot of trouble. eald, just use xmodmap, saves you a lot of trouble.

]]> By: Linux input model http://blogs.gnome.org/hughsie/2008/07/04/linux-input-model/comment-page-1/#comment-500 Linux input model Fri, 04 Jul 2008 18:49:21 +0000 http://blogs.gnome.org/hughsie/2008/07/04/linux-input-model/#comment-500 [...] Go to the author’s original blog: Linux input model [...] [...] Go to the author’s original blog: Linux input model [...]

]]> By: eald http://blogs.gnome.org/hughsie/2008/07/04/linux-input-model/comment-page-1/#comment-498 eald Fri, 04 Jul 2008 17:46:17 +0000 http://blogs.gnome.org/hughsie/2008/07/04/linux-input-model/#comment-498 Any of this explains why Dvorak is broken in Gnome? Regards Any of this explains why Dvorak is broken in Gnome?

Regards

]]> By: MDK http://blogs.gnome.org/hughsie/2008/07/04/linux-input-model/comment-page-1/#comment-497 MDK Fri, 04 Jul 2008 17:10:56 +0000 http://blogs.gnome.org/hughsie/2008/07/04/linux-input-model/#comment-497 What a mess. What a mess.

]]>