On Wed, 8 Dec 2010, Jacob Meuser wrote: <snip> > great. but, what if we need to interrupt the transfer. we don't want > to hang here. > > well, this function takes a timeout. so, it's possible to make it > return, even if the transfer stalls. but is this used? I looked > at the ports that use libusb. setting 0/infinite timeout for bulk > transfers is extremely rare, only set in code marked experimental > or problematic. in the kernel, there are however some callers that > use USBD_NO_TIMEOUT. > > so, I offer the following. if there's no timeout, behave like we do > now and catch signals, and if there's a timeout, ignore signals. > > I did the same for interrupt transfers because the situation seems > to be the same. > > thoughts?
For what it's worth this diff fixed all remaining issues that were left with scanning and libusb for me. So I'll be happy if it (or a variarion) gets committed. Thanks Jacob. -- Antoine
