[LINUX5250] More 122 agony.

[Phillip.Watts@xxxxxxxxx]

This may be getting to be off topic but i'll throw
it out because keyboards ARE getting weirder with
all the new devices.

Thanks VERY MUCH to the patience of this group I can now.

Map a keysym such as  Control_R to a string "\015" in .Xdefaults.
And I can map a keycode to a keysym with xmodmap.

2/3 of the way there.

But I can't map a scancode to a keycode for X.
( I'm starting to dislike X mucho. Of course I feel like an ungrateful
   twerp because it took mountains of effort, its all we have, and
    its much better that win32 SDK)

My 122 keyboard does not have all its scancodes mapped.  ? : ( ?
With getkeycodes I can find out which scancodes have been mapped
    to which keycodes.
With showkeys I can determine all the scancodes.
With setkeycodes I can map a scancode to a keycode
So now I have scancode e06a( F23) mapped to keycode 114.
getkeycodes and keyboard tests reveal this to be true.

But when I go to X and do xev,  it reveals the old garbage mapping.
Aaaah!  X does not use the kernel scancode to keycode map !

Nowhere can I find out how to deal with scancodes in X without going into the
source.  Anyone got a clue?