lkml.org 
[lkml]   [2003]   [Jul]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: 2.6.0-test1-ac2 issues / Toshiba Laptop keyboard
From
Date
>>>>> "Ralf" == Ralf Hildebrandt <Ralf.Hildebrandt@charite.de> writes:

Ralf> * and the most interesting issue is related to the keyboard of this
Ralf> Toshiba laptop (Satellite Pro 6100):

Ralf> The Kernel reports:

Ralf> atkbd.c: Unknown key (set 2, scancode 0xb2, on isa0060/serio0) pressed.
Ralf> atkbd.c: Unknown key (set 2, scancode 0xae, on isa0060/serio0) pressed.
Ralf> atkbd.c: Unknown key (set 2, scancode 0xb1, on isa0060/serio0) pressed.
Ralf> atkbd.c: Unknown key (set 2, scancode 0x97, on isa0060/serio0) pressed.
Ralf> atkbd.c: Unknown key (set 2, scancode 0xa2, on isa0060/serio0) pressed.
Ralf> atkbd.c: Unknown key (set 2, scancode 0x92, on isa0060/serio0) pressed.

I've been hacking through a similar issue on some Dell laptops.

You need to add entries to the atkbd_set2_keycode[] array in
drivers/input/keyboard/atkbd.h. Look at the #defines in
inlucde/linux/input.h for stuff that matches the keys that
five the unknown key printk()s, and put those values in the
Nth entry of the array, where N is the scancode reported in
the printk().

Eg, if the first key mentioned above were a VolumeUp key, you
would want to add the value 115 to the 0xb2'th entry in the
array.

Once you do that, you can run xev(1x) to see what X keycode they
get, look in xkb/keycodes/xfree86 for the symbol associated with
each keycode, and in xkb/symbols/* for something that associates
that xkb symbol with an X11 keysym.
-JimC

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:46    [from the cache]
©2003-2011 Jasper Spaans