linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Meaning of match_flag (and other .map fields)
Date: Wed, 07 Mar 2001 14:18:55 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98397487428881@msgid-missing> (raw)

> Where can I find informations about the maning of match_flag and of the 
> other flags? 

In <linux/usb.h> as of 2.4.0 and later, USB_DEVICE_ID_* tell what
those bits in match_flags do.


> In usb.c I've found the same tests that are done by usb.agent? why this 
> dupication of code?

The kernel (usb.c) does those tests for drivers that are loaded.
User mode code (usb.agent) makes sure such drivers get loaded,
so the kernel (usb.c) can actually bind the drivers.

Eventually I can see the user mode code becoming more intelligent
about driver binding ... some drivers may be better for some devices
than others, for example.  And maybe that'd mean changing how the
kernel does binding (say, only at the request of user mode code)
in some cases ... Adam's note (from a week or two back) seemed
to imply some of that.

- Dave



_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2001-03-07 14:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-07 14:18 David Brownell [this message]
2001-03-07 14:35 ` Meaning of match_flag (and other .map fields) Gioele Barabucci

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=marc-linux-hotplug-98397487428881@msgid-missing \
    --to=david-b@pacbell.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).