Hi , Thanks, The error -32 now become -75 when I use 2.4.17. I tried the kernel 2.4.17 but it generate a error -75. .... Dec 28 17:39:12 desktop kernel: Element != First TD
Dec 28 17:39:12 desktop kernel: 0: [c13e71e0] link (013e7210) e3 Length=7 MaxLen=7 DT0 EndPt=0 Dev=3, PID=2d(SETUP) (buf=0297a62c) Dec 28 17:39:12 desktop12 kernel: 1: [c13e7210] link (013e7240) e3 SPD Stalled Babble Length=7 MaxLen=7 DT1 EndPt=0 Dev=3, PID=69(IN) (buf=0515b8c4) Dec 28 17:39:12 desktop12 kernel: 2: [c13e7240] link (00000001) e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0 Dev=3, PID=e1(OUT) (buf=00000000) Dec 28 17:39:12 desktop12 kernel: Dec 28 17:39:12 desktop12 kernel: usb.c: USB device not responding, giving up (error=-75) > | I still could not solve the USB problem of the Transilica bluetooth > | Evaluation Kit http://www.transilica.com/prod.html, in kernel 2.4.9. > | ... > | > | Dec 21 13:18:14 desktop12 kernel: usb.c: USB device not responding, giving > | up (error=-32) > | > | Dec 21 13:18:14 desktop12 kernel: hub.c: USB new device connect on bus1/1, > | assigned device number 5 > | > | > | I also put the vendor information (03e8-03ef) into the > | /usr/src/linux***/drivers/pci/pci.ids and > | /usr/src/linux***/drivers/pci/devlist.h. > | In detail, What I have done in the above directory was: VENDOR(03e8,"Transilica(Microtune) Pte. Ltd. ") DEVICE(03e8,03ef,"1760") ENDVENDOR() > linux/include/asm/errno.h > > then look in: > > linux/Documentation/usb/error-codes.txt > In the above error files I found that the -32 means #define EPIPE 32 /* Broken pipe */ error -75 means #define EOVERFLOW 75 /* Value too large for defined data type */ This EOVERFLOW is not a conversional error for the USB bacause I could not find it in the linux/Documentation/usb/error-codes.txt file. I have looked through the usb.c file and try to understand why the pipe is broken and why it is over flowed in 2.4.17 but. When I read till the stage of URB part, I could not understand now. I am not asking you to explain the usb.c for me. I will keeping on trying. My questions are: Is the usb.c file meant for USB spec 1.1 or 2? Have anyone of you encounter the similar problem? Can I include a new usb device my modify the devlist.h file in pci directory? What are the possible cause for the EOVERFLOW or EPIPE? Thanks, Best Regards, David _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
