On Fri, 23 Feb 2007, Guenther Sohler wrote: > Odkud jste.? Mam Cesky zenu tak umim mluvit trochu cesky!
Herzliche grusse aus Prag :) > If you look at the function stack i described earlier, you see that > there is the function 'input_sync' which calls the function > 'input_event'. Input sync gets the parametes from the function call in > "input_sync" but with this parameters submitted, "input_event" will > NEVER call the event function of the evdev device. Sorry, but this is not true - the evdev_event() is invoked at the very end of input_event(). > I have done so. I have directly changed to source code to ALWAYS dump > the debug data. I see the bytes from the remote control (there are 4 > bytes per event) and they are properly processed in HID. I am using > 2.6.20 kernel. Could you please post the debug data? Probably the HID events are just not properly mapped to input events (either due to missing mapping in hid-input, or due to the remote control sending broken events that hid-input is not currently able to reproduce without adding some quirk - both is possible). -- Jiri Kosina ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
