Greg KH wrote:
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.

Yes, something changed there.  Here's a patch from Pat Mochel to
possibly fix this problem.  I haven't tested it yet, so use it at your
own risk (and let me know if it works for you...)
Well, the first sanity tests passed, which they didn't do before:
the driver bound just fine through hotplug, and after rmmod/modprobe
it also bound. I'm not sure when I'll have a chance to try more
with this, but so far it looks good! And it starts to make 2.5.58
usable, at least on systems where the console works outside X11.

Thanks!

- Dave






-------------------------------------------------------
This SF.NET email is sponsored by: A Thawte Code Signing Certificate is essential in establishing user confidence by providing assurance of authenticity and code integrity. Download our Free Code Signing guide:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to