I'd built a kernel with both 'hid' and 'usbkbd' support.
When I hotplugged a keyboard, both drivers loaded (as
they should), and "usbkbd" bound to the device (one of
them had to win, that was it). So far so good.
Now "rmmod usbkbd" ... and hey, the device didn't get
re-bound! I had to "rmmod hid" and "modprobe hid"
before that happened. It was supposed to happen
automatically when "usbkbd" was removed. I'm fairly
sure this wasn't a problem with the 2.5.43 patches I
had submitted to fix other driver binding problems.
Unrelated: "usbkbd" still shows up in usbfs as being
the "keyboard" driver. Can we yet use MODULE_NAME to
get rid of such problems? :)
- Dave
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0003en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
