|
From: James S. <jsi...@li...> - 2001-03-27 20:25:43
|
>Is there something special that i miss? Do i have to create any special >devices in /dev/... ? All input devices can be accessed threw /dev/input/eventX. Take a look at dmesg. You should see all your /dev/eventX devices registered. Do this after you run inputattach. For example I have a serial mouse. I do a inputattach -ms /dev/ttyS1. Then reading dmesg I see a message similar to: input3: Serial Mouse on serio0 event3: Event device for input3 Now you know everything is working :-) Now to test it ... >How to debug the whole process? Is evtest usefull for that - or does it >primarly deal with joystick devices / mice? .. with evtest. Every input device, keyboard, mouse, touchscreen etc has a /dev/input/eventX associated with it. Just run evtest on the proper /dev/input/eventX and you will see it work. Test it with that device. For 2.4.X the events of the keyboard should to to the console. With this versus all keyboard events go to the console system. In the CVS tree we have. The keyboards are attached to a specific VT. If you make 3 keyboards and 3 video cards they will all behave as a seperate terminal independent of each other. Data from one keybaord will not end up on another workstation. MS: (n) 1. A debilitating and surprisingly widespread affliction that renders the sufferer barely able to perform the simplest task. 2. A disease. James Simmons [jsi...@li...] ____/| fbdev/console/gfx developer \ o.O| http://www.linux-fbdev.org =(_)= http://linuxgfx.sourceforge.net U http://linuxconsole.sourceforge.net |