Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

editor scanning same usb codes as mouse uses?

Help
Rick Berge
2008-11-17
2013-04-17
  • Rick Berge
    Rick Berge
    2008-11-17

    I'm using keytouch 2.4.1 and editor 3.2.0 beta with a fairly old Logitech set (Y-RE20 kbd, M-RR63 mouse), usb-connected.  Oh, and I'm running a Gentoo 2.6.25 kernel.

    I started using keytouch several months ago, and the most important media keys worked (play/pause, etc), so I was happy.  With the recent usb support, I figured I'd go back and fix the rest of the buttons.

    Problem is, the editor is reporting several key usb-codes that are the same as mouse button codes (e.g. Shopping is 0x90001 same as M1, iTouch is 90002 as M2, etc).  Which would be nice if I wanted to replace my mouse with my keyboard... :)

    Anyway, I'd like to track this down so that either the kernel or keytouch (or X) can be fixed.  Here's a peek at some of the event handling.  Looks like there are at least some differences in the higher-order info next to the press/release direction indication.

    % cat /dev/input/event1 | od -tx1

    #mouse 1 press
    0000000 b9 a2 21 49 21 5e 0a 00 04 00 04 00 01 00 09 00
    0000020 b9 a2 21 49 2d 5e 0a 00 01 00 10 01 01 00 00 00
    0000040 b9 a2 21 49 43 5e 0a 00 00 00 00 00 00 00 00 00

    #mouse 1 release
    0000060 c2 a2 21 49 be 48 0d 00 04 00 04 00 01 00 09 00
    0000100 c2 a2 21 49 c8 48 0d 00 01 00 10 01 00 00 00 00
    0000120 c2 a2 21 49 db 48 0d 00 00 00 00 00 00 00 00 00

    #"shopping" press
    0000140 d3 a2 21 49 4e aa 06 00 04 00 04 00 01 00 09 00
    0000160 d3 a2 21 49 57 aa 06 00 01 00 00 01 01 00 00 00
    0000200 d3 a2 21 49 5f aa 06 00 00 00 00 00 00 00 00 00

    #"shopping" release
    0000220 d7 a2 21 49 99 a2 07 00 04 00 04 00 01 00 09 00
    0000240 d7 a2 21 49 a3 a2 07 00 01 00 00 01 00 00 00 00
    0000260 d7 a2 21 49 ac a2 07 00 00 00 00 00 00 00 00 00

    On a second topic, I noticed that some of the keycodes don't work.  For instance, the Media key was assigned MEDIA and didn't work until I assigned it another one, like CONFIG.  This sounds similar to "Key 178 doesn't working on Logitech Keyboard" thread.