--- snip --- > The HID module talks to the Input subsystem. The input subsystem outputs to a > range of output device. You need the event interface (/dev/input/eventX, > where X is 0..31). You can just read events out using a standard read() call. > > I have a tutorial that is close enough to done to help you with this, though > by no means complete. I'll try to get it up on a suitable web site soon, and > post a link. > > Brad > --- snop ---
Right on the spot Although I were not able to get this working immediately, some research in the documentation indicated that I needed to load the module evdev.After that, I could see the binary data on the /dev/input/event0 and /dev/input/event1 interface. The data is probably binary scancodes. I'll get on with that tomorrow. However, the data is still being interpreted by the application, what is the most simple way to prevent that ( apart from not enabling the modules mousedev and keybdev ( in the drivers/input directory )? I know there is an usb hotplug script which may need some changes? I would like the mouse events to pass through, but the keyboard events to be trapped for this device only. Such that I can use the mouse under X, but lirc for shortcut keys. Way cool that would be. Thank you. TTFN, Hans E. _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
