Created attachment 20022 [details] [review]
patch

Created attachment 20023 [details]
init script

The contributor also provided this init script to enable the keyboard, however I'm not sure how necessary this is.

The mapping is very similar to "microsoftmult" model, except for those keys:
key K66 { [ XF86Reply ] };
key I6F { [ XF86Documents ] };
key K63 { [ XF86New ] };
key K64 { [ XF86Open ] };
key K65 { [ XF86Close ] };

Could the init script be changed to make mapping exactly same as microsoftmult? That way I'd just add the alias...

Created attachment 21557 [details]
Updated section of symbols

Just in case, I updated symbols (using "include" and sorting keycodes)

I added the init script because the kernel told me that I had to call setkeycodes:
atkbd.c: Use 'setkeycodes e064 <keycode>' to make it known. 

I will check if this is still necessary with current kernels.

Unfortunatly this does not work anymo(In reply to comment #3)
> The mapping is very similar to "microsoftmult" model, except for those keys:
> key K66 { [ XF86Reply ] };
> key I6F { [ XF86Documents ] };
> key K63 { [ XF86New ] };
> key K64 { [ XF86Open ] };
> key K65 { [ XF86Close ] };
> 
> Could the init script be changed to make mapping exactly same as microsoftmult?
> That way I'd just add the alias...
> 

Actually this mapping does not work anymore. The keycodes set with setkeycode do not match to the X keycodes from either evdev or xfree86 so the layout is totally bogus now :-/

(In reply to comment #6)
Jens, I suspect you're using evdev now? Do evdev keycodes work ok for you?

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/31.