Sorry if it's double post. I just got a failed mail notifikation. > > // Now, I return ENODEV from probe > > At this point the USB core gives up on trying to > find a driver for your > device. As it should. It doesn't ignore your > ENODEV. > > But it still goes ahead trying to find drivers for > these two other > devices. Again as it should. (Although I would > expect 1-4.3 to get > address 15, not 14, since 14 was already assigned to > 1-4.2.)
That was address 15 not 14 (typo). >The USB core re-registers the device on its own, and >that re-registration causes your driver's probe >routine to be called. >From a previous post, I came to understand that when the reset_device fails and returns ENODEV, USB core re-registers the failed device and reloads my driver. Shouldn't it pick the failed device before moving onto the next one? It didn't - that's what I meant when I said it ignored ENODEV.. Is that the right behavior? If I want to reset a device, when I'm no longer in probe, how do I do a reprobe? I suppose I'm not allowed to call probe() directly from the driver - right? Thanks.. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
