Kari Hameenaho wrote:

This seems to have started in 2.5.57, finding the devices at boot used to work in 2.5.56.
I was wonder if the probing logic (driver core) got something
wrong ... I just saw a situation where modprobing the driver
wouldn't make it bind to devices that were already present.
It had to be the other way around: driver first, then device.

- Dave





-------------------------------------------------------
This SF.NET email is sponsored by: Take your first step towards giving your online business a competitive advantage. Test-drive a Thawte SSL certificate - our easy online guide will show you how. Click here to get started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel


Reply via email to