> > > HCD and USB core do not unlink URBs on device disconnect because currently > > > it is driver's responsibility. > > > >Not entirely true. OHCI tries to safeguard against broken drivers, > >and in 2.5 anything using the new HCD code in usbcore does the > >same safeguarding. (Such as EHCI ...) The UHCI drivers may do > >things differently. > > Actually I would not call it broken driver. I think it make sense for HCD > or USB core to cancel all outstanding requests prior to calling 'disconnect'.
Not without (a) defining a new URB status code to indicate "canceled due to disconnect, and (b) doing a major rework of the relationship between the hub driver and the HCDs. It'd be possible to do (b) in the context of 2.5, but that'd be a fair amount of work. Are you volunteering to help change all the HCDs, and the hub driver? And all the other parts of usbcore that'd be affected by such a change? > Why can't HCD just cancel them itself before calling > disconnect ? As I wrote earlier, the HCD isn't calling disconnect. It's the hub driver. - Dave _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
