From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott James Remnant Date: Thu, 12 Mar 2009 10:21:07 +0000 Subject: Re: USB driver assignment with udev Message-Id: <1236853267.6339.138.camel@quest> MIME-Version: 1 Content-Type: multipart/mixed; boundary="=-/6cGJgJoasz06hWkDn5X" List-Id: References: In-Reply-To: To: linux-hotplug@vger.kernel.org --=-/6cGJgJoasz06hWkDn5X Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2009-03-11 at 23:20 +0000, Steve Calfee wrote: > I have a different situation, but a classic issue is if a user wants to > have ub handle one device and usb-storage handle others. How can this be > done? udev loads the driver, but the driver itself grabs the devices. The > first module loaded will hog all the devices. USBIP will also sooner or > later hit this problem, some devices might need to be local and some plac= ed > remotely. Presumably separate drivers will be needed. >=20 That's simple. ub includes an alias for the specific device (ie. by vendor/device id as well as class). usb-storage includes the generic classful alias. ub appears before usb-storage in the kernel link order, and thus appears first in /lib/modules/$(uname -r)/modules.order So the kernel will try that module first if it's a built-in, and modprobe will try load module first if not. If you want to do more complicated runtime decisions, you can use the bind/unbind interface. Scott --=20 Scott James Remnant scott@canonical.com --=-/6cGJgJoasz06hWkDn5X Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAkm44hMACgkQSnQiFMl4yK64bwCgiwaukTNcmsxd+D4ql2xv6Ier xLYAn3NMPaHrqUAn0BwYgWcFpGHMGNIy =ypDx -----END PGP SIGNATURE----- --=-/6cGJgJoasz06hWkDn5X--