The only justification I can see is to disconnect to stuff that's been unplugged or misbehaves.
In your case that's not true. brucee On Sun, Jul 19, 2009 at 5:16 PM, <[email protected]> wrote: > from the manpage: > > For control, bulk, and isochronous transfers, there is an > implicit timeout performed by the kernel and it is not nec- > essary for applications to place their own timers. For > interrupt transfers, the kernel will not time out any opera- > tion. > > souldnt the application / userspace driver know better than some > random choosen timeout in the kernel driver? > > also, this has not been taken into account for the new usb/ether. > > for now i'll just compare the errstr and try again, but this implicit > timeout stuff just smells "too smart" for me. > > -- > cinap > > >
