On Fri, 23 Feb 2007, Guenther Sohler wrote: > Some weeks before I have already reported about problems with my USB > Remote control which I obtained from eBay. I got a remote control sender > and a IR receiver with an USB cable, which I plug into my computer. I > expect receiving the events through /dev/input/event7 but it does not > work out. > The only chance to receive an event is > * i plug in the receiver > * i press a button on the remote control > * i cat /dev/input/event7 > Starting on that i cannot receive more events unless i unplug the cable > and plug it again. > drivers/usb/input/hid-core.c: hid_irq_in > drivers/hid/hid-input.c: hid_input_report > include/linux/input.h: input_sync > drivers/input/input.c:input_event > <======== BROKEN PIPE =========> > drivers/input/evdev.c:evdev_event > evdev->wait waitqueue > drivers/input/evdev.c:evdev.c
Hi Guenter, what does the "BROKEN PIPE" sign exactly mean here? Does the cat /dev/input/event7 get -EPIPE error, or does it mean anything else? Also, could you please be more specific what kind of remote control (vendor/product) is that? > At the denoted place <======Broken Pipe ==> In the function input_event > with the configuration sent from input_sync it will NOT call the event > function from evdev. Thus it does not know that new data is available. > Maybe hid_input_report should call another function but input_sync > instead ... Sorry, I don't fully understand this paragraph, could you be please more specific? Could you please also try to build hid and usbhid in debugging mode, so that we could see better what is happening (though from your description of the problem it is not clear to me whether the problem is in hid-input or input)? If you are using 2.6.21-rc1, this could be accomplished by setting HID debug in kernel configuration menu. If you are using older kernel, you'd have to define DEBUG and DBEUG_DATA macros in drivers/hid/hid-core.c, drivers/hid/hid-input.c and drivers/usb/input/hid-core.c > Maybe somebody can point me out a better mailing list to ask, because my > problem is not only USB related, but expands about usb, input driver, > HID driver. Looking at the output of usbmon, the usb part actuallyt > seems to work quite fine. The Only problem seems the transmission of the > events to /dev/input/event7 I added Dmitry to CC. -- 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 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
