From: Johannes E. <joh...@er...> - 2003-03-17 00:38:00
|
-103 (on x86 atleast) is -ECONNABORTED. That looks like it's a timeout condition. Are you using usb-uhci? I've checked in some changes that should handle the timeout case better. However, you're writing which would mean in this case the device kept on NAKing, assuming the code in libusb is correct. That's kinda rare, so I don't think that would happen. What is LINUX_USB_TIMEOUT set to? Unfortunately, I don't have easy access to any devices that use interrupt endpoints, so I'm testing this with a duplicate of this function but using control transfers. JE On Mon, Mar 17, 2003, David Glance <da...@cs...> wrote: > I'm getting a status -103 now. > > Johannes Erdfelt wrote: > > >I found 2 problems in the code I checked in, one that would result in > >this error (we didn't set the signal number, because we don't use it, > >but the kernel wants it to be 0 in that case), the other would always > >return 0 on success (instead of the actual size of data returned). > > > >I've checked in fixes for those now. Can you update from CVS and try > >again? > > > >JE > > > >On Sun, Mar 16, 2003, David Glance <da...@cs...> wrote: > > > > > >>I have tried this with the lego usb tower and I am getting the following > >>error on writing: > >> > >>USB error: error submitting interrupt URB: Invalid argument > >> > >>I am calling this function using the following: > >> > >> usb_interrupt_write(tower->dev, tower->outepoint | UT_WRITE, (char *) > >>buf, nbytes, LINUX_USB_TIMEOUT); > >> > >>Any ideas what the invalid argument is? > >> > >>Thanks > >> > >>David > >> > >> > >>Johannes Erdfelt wrote: > >> > >> > >> > >>>I checked in some code to CVS which has a prototype implementation for > >>>synchronous interrupt transfer support. > >>> > >>>It compiles, but is untested so far. It still needs some more work > >>>(finer grained timeouts via setitimer) and support for larger buffers > >>>(limited to page size, 4096 on i386, right now). > >>> > >>>Not to mention support from BSD and MacOS X too :) > >>> > >>>If someone tries it, let me know your results. > >>> > >>>JE > >>> > >>> > >>> > >>>------------------------------------------------------- > >>>This SF.net email is sponsored by:Crypto Challenge is now open! > >>>Get cracking and register here for some mind boggling fun and > >>>the chance of winning an Apple iPod: > >>>http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > >>>_______________________________________________ > >>>Libusb-devel mailing list > >>>Lib...@li... > >>>https://lists.sourceforge.net/lists/listinfo/libusb-devel > >>> > >>> > >>> > >>> > >>> > >>> > >> > >>------------------------------------------------------- > >>This SF.net email is sponsored by:Crypto Challenge is now open! > >>Get cracking and register here for some mind boggling fun and > >>the chance of winning an Apple iPod: > >>http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > >>_______________________________________________ > >>Libusb-devel mailing list > >>Lib...@li... > >>https://lists.sourceforge.net/lists/listinfo/libusb-devel > >> > >> > > > > > >------------------------------------------------------- > >This SF.net email is sponsored by:Crypto Challenge is now open! > >Get cracking and register here for some mind boggling fun and > >the chance of winning an Apple iPod: > >http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > >_______________________________________________ > >Libusb-devel mailing list > >Lib...@li... > >https://lists.sourceforge.net/lists/listinfo/libusb-devel > > > > > > > > > |