Re: Still Problems with USB Remote control
"Guenther Sohler" <[email protected]>
| Newsgroups | gmane.linux.usb.devel |
|---|---|
| Message-ID | <[email protected]> |
Ahoj Jiri Odkud jste.? Mam Cesky zenu tak umim mluvit trochu cesky! Thank you for your valubale reply! > 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? No, "BROKEN PIPE" means, that there is a disconnection in the data flow. > > Also, could you please be more specific what kind of remote control > (vendor/product) is that? Sorry I dont have that information available at the moment. But I have posted 2 weeks before about that topic, and there all this information is available. there is written "Asus" on the remote, but the usb receiver is called something like "eDio FX ...". > > 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 ... 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. > 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. 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. > > 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 Thank you again for your interest into my problem. Guenther -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer ------------------------------------------------------------------------- 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