2.6.9 Kernel + 3780 Keyboard

[Mock, JV Jason (6278) @ IS]

	Iâm doing some work on attempting to get an old 3780 keyboard (yes
those old 34 function key IBM/AT keyboards are still wondering around)
working on a 2.6.9 kernel system.  The keyboard of course use to work on
2.4.x system, as long as we forced the keyboard to scancode set 3 (some keys
were creating the same keycodes with scancode set 2).  Now, with the 2.6.x
kernel, we are seeing a much more serious problem as many scancodes appear
to be âmovedâ from one key to another (I.E.  I can run showkey âs against
the 2.4 system, and document the scancodes for specific keys, and if I do
the same for 2.6, many of the function buttons, including home, insert, and
etc are different).  That being said they are at least consistently
different in a way that can be documented and mapped.  The problem then
become, the second I start mapping these scancodes to they keys dictated by
âinclude/linux/input.hâ, I start loosing other keys.  Then, after they are
mapped, showkey âs reports different scancodes for the mapped keys.  ???
This is only the beginning as the left control key never reports a break (as
showkey âs indicates) and even if I do get keys mappedâ  if I verify the
keycode they are mapped to against showkey and xev, I get two completely
different answers.   (I.E.  I map scancode 64 (which is what the F13 button
is coming up as) to keycode 108 (indicated by input.h).  I run showkey,
press the F13 key, and I get keycode 108â what I expectâ  then I run xev and
get 105?!).  I guess we are just trying to understand how much of this is
due to the changes in keyboard input between the 2.4 kernel and the 2.6
kernel and if there is a simple solution to our problem.  While I realize
the xev issue is probably better directed at Xorg, because even if I get
that fixed, I have keys that die the second I map and others that donât have
breaks.  Vojetch, what am I doing wrong? â

Thanks,

Jason Mock
-
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/