From: Ralf A. <ra...@KO...> - 2001-03-27 19:38:10
|
Hello, i try using a serial sun5 keyboard on an x86 system. I've used the adapter described at the "Linux Input Project" site - and can see characters arriving on keypress / release when using e.g. minicom on the serial port the keyboard is attached to. Unfortunately i fail to get the keyboard itself working I'm using Linux 2.4.1. I do an insmod .../serial.o insmod .../serio.o insmod .../serport.o inputattach -skb /dev/ttyS0 & insmod .../input.o insmod .../evdev.o insmod .../keybdev.o but apart from an entry Mar 27 23:01:16 dell kernel: serio0: Serial port tts/0 in /var/log/messages i don't get any further reaction. Is there something special that i miss? Do i have to create any special devices in /dev/... ? How to debug the whole process? Is evtest usefull for that - or does it primarly deal with joystick devices / mice? Any hints will be highly appreciated - i'm just doing a version of an PS/2-to-serial adapter for attaching PS/2 (chording) keyboards (like the Handykey Twiddler2 http://www.handykey.com) to a Compaq iPAQ PDA running Linux - but testing / developing with the serial Sun5 keyboard on an x86 system makes development much easier. Best regards ralf |
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 |
From: Ralf A. <ra...@KO...> - 2001-03-27 20:38:50
|
Many thanks, just getting sunkbd.c from the CVS and loading the compiled module worked perfectly!! regards ralf -- Best regards, Ralf Ackermann |
From: Vojtech P. <vo...@su...> - 2001-04-26 10:15:02
|
On Tue, Mar 27, 2001 at 10:38:29PM +0200, Ralf Ackermann wrote: > Many thanks, > > just getting sunkbd.c from the CVS and loading the compiled module worked > perfectly!! Glad to hear that. -- Vojtech Pavlik SuSE Labs |
From: Vojtech P. <vo...@su...> - 2001-04-26 10:14:58
|
On Tue, Mar 27, 2001 at 09:36:26PM +0200, Ralf Ackermann wrote: > Hello, > > i try using a serial sun5 keyboard on an x86 system. > I've used the adapter described at the "Linux Input Project" site - and > can see characters arriving on keypress / release when using e.g. minicom > on the serial port the keyboard is attached to. > > Unfortunately i fail to get the keyboard itself working > I'm using Linux 2.4.1. > I do an > insmod .../serial.o > insmod .../serio.o > insmod .../serport.o > > inputattach -skb /dev/ttyS0 & > > insmod .../input.o > insmod .../evdev.o > insmod .../keybdev.o > > but apart from an entry > Mar 27 23:01:16 dell kernel: serio0: Serial port tts/0 > in /var/log/messages i don't get any further reaction. > > Is there something special that i miss? sunkbd.o > Do i have to create any special > devices in /dev/... ? > How to debug the whole process? Is evtest usefull for that - or does it > primarly deal with joystick devices / mice? Evtest will work once the device is found. You're still missing the most important driver of the stack. -- Vojtech Pavlik SuSE Labs |