Re: Meaning of match_flag (and other .map fields)

Re: Meaning of match_flag (and other .map fields)

[David Brownell]

> 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

Meaning of match_flag (and other .map fields)

[Gioele Barabucci]

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

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

-- 
Gioele Barabucci (Gb]) 
) mailto:dev@gioelebarabucci.com
) http://www.gioelebarabucci.com
) ) I've been and now I've gone
) )          /Magic Pie^Oasis


_______________________________________________
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