All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott James Remnant <scott@canonical.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: USB driver assignment with udev
Date: Thu, 12 Mar 2009 10:21:07 +0000	[thread overview]
Message-ID: <1236853267.6339.138.camel@quest> (raw)
In-Reply-To: <loom.20090311T231825-449@post.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]

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 placed
> remotely.  Presumably separate drivers will be needed.
> 
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
-- 
Scott James Remnant
scott@canonical.com

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-03-12 10:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11 23:20 USB driver assignment with udev Steve Calfee
2009-03-11 23:37 ` Greg KH
2009-03-12  0:32 ` Steve Calfee
2009-03-12  0:35 ` Kay Sievers
2009-03-12  2:01 ` Greg KH
2009-03-12 10:21 ` Scott James Remnant [this message]
2009-03-12 23:01 ` Steve Calfee
2009-03-12 23:59 ` Kay Sievers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1236853267.6339.138.camel@quest \
    --to=scott@canonical.com \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.