some keys are still not working, please take a look at: http://bugs.gentoo.org/show_bug.cgi?id=84844 for more details.
Could you please have a look at the current xkeyboard-config code - and prepare the patch, if it is still necessary? Thanks
by current you mean xorg-x11-7.0 and by xkeyboard-config code, you mean the source of a program with that name, or just the configs? btw, most kernels usb-core.c needs to be patches against an hardware manufacture provided patch, to make really all keys work. i have yet to figure out, how to do that correctly and this is porbably something i should send to the kernel-dev-list.
(In reply to comment #2) > by current you mean xorg-x11-7.0 and by xkeyboard-config code, you mean the > source of a program with that name, or just the configs? I mean separate XKB data repository hosted on freedesktop.org. Which in future will be merged into xorg. http://www.freedesktop.org/wiki/Software_2fXKeyboardConfig > provided patch, to make really all keys work. i have yet to figure out, how to > do that correctly and this is porbably something i should send to the > kernel-dev-list. I'd say so... Sergey
sorry, that i haven't answered for so long, but i didn't want xorg-x11 7.0 install before it went life on my distro. now that this has happend, i've encountered, that there is in fact a "cymotionlinux" xkbmodel, which is mostly working. is it any use to you, if i tell you which keys do not work at all and which are assigned the wrong maps?
Well, if you just send me a patch...;)
is that ok? the only "problem" left ist, a key on the keyboard, that isn't recognized at all. it's a "K" key, left of the "Tux" key and right of the LCONTROL key. this might be a kernel issue, but i don't really know. root@enti $ diff -p symbols/inet.original symbols/inet *** symbols/inet.original 2006-03-25 12:36:37.000000000 +0100 --- symbols/inet 2006-03-25 13:17:25.000000000 +0100 *************** xkb_symbols "cymotionlinux" { *** 2096,2112 **** key <I24> { [ XF86AudioStop ] }; key <I10> { [ XF86AudioPrev ] }; key <I19> { [ XF86AudioNext ] }; key <I21> { [ XF86Calculator ] }; key <I6C> { [ XF86Mail ] }; key <I02> { [ XF86WWW ] }; key <I63> { [ XF86Standby ] }; ! key <ALT> { [ XF86ScrollUp ] }; key <I0F> { [ XF86ScrollDown ] }; key <I3C> { [ XF86Cut ] }; key <I78> { [ XF86Copy ] }; key <I1F> { [ XF86Launch1 ] }; key <I17> { [ XF86Launch2 ] }; key <I2B> { [ XF86Launch3 ] }; ! key <AE13> { [ Redo ] }; key <I07> { [ Undo ] }; }; --- 2096,2114 ---- key <I24> { [ XF86AudioStop ] }; key <I10> { [ XF86AudioPrev ] }; key <I19> { [ XF86AudioNext ] }; + key <K6C> { [ XF86AudioEject ] }; key <I21> { [ XF86Calculator ] }; key <I6C> { [ XF86Mail ] }; key <I02> { [ XF86WWW ] }; key <I63> { [ XF86Standby ] }; ! key <K75> { [ XF86ScrollUp ] }; key <I0F> { [ XF86ScrollDown ] }; key <I3C> { [ XF86Cut ] }; + key <K65> { [ XF86Paste ] }; key <I78> { [ XF86Copy ] }; key <I1F> { [ XF86Launch1 ] }; key <I17> { [ XF86Launch2 ] }; key <I2B> { [ XF86Launch3 ] }; ! key <I0A> { [ Redo ] }; key <I07> { [ Undo ] }; };
Committed (with some effort, because the patch was not for xkeyboard-config). Could you please check xkeyboard-config CVS whether it is ok now.
well actually, there are two entries missing. it would be also easier to compare the differences, if the entries wouldn't be sorted by the keymaps but the names. You've deleted the entries: key <ALT> { [ XF86ScrollUp ] }; key <AE13> { [ Redo ] }; but they should instead only be altered, to read: key <K75> { [ XF86ScrollUp ] }; key <I0A> { [ Redo ] };
Thanks, fixed.
i made another mistake. please correct. the patch is against the latest cvs of xkbdesc --- symbols/inet.original 2006-04-01 12:27:21.000000000 +0200 +++ symbols/inet 2006-04-01 12:27:28.000000000 +0200 @@ -1972,7 +1972,7 @@ key <I6C> { [ XF86Mail ] }; key <I78> { [ XF86Copy ] }; key <K65> { [ XF86Paste ] }; - key <K6C> { [ XF86AudioEject ] }; + key <K6C> { [ XF86Eject ] }; key <K75> { [ XF86ScrollUp ] }; key <XFER> { [ XF86AudioMedia ] }; };
It is all in git now, for quite a while
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.