[lkml]   [2003]   [Nov]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: file2alias - incorrect? aliases for USB
On Monday 10 November 2003 12:37, Greg KH wrote:
> On Sun, Nov 09, 2003 at 09:55:19PM +0300, Andrey Borzenkov wrote:
> > file2aliases puts in alias device ID high and low numbers directly from
> > match specifications. E.g. for this match table entry:
> >
> > usb-storage 0x000f 0x04e6 0x0006 0x0100 0x0205
> > ...
> >
> > it generates alias
> >
> > alias usb:v04E6p0006dl0100dh0205dc*dsc*dp*ic*isc*ip* usb_storage
> >
> I would suggest just ignoring the bcdDevice value, and loading all
> modules that match the idVendor and idProduct values, and let the kernel
> sort it out :)

the obvious point that this leaves unneeded modules in kernel aside ...

that won't work that easy. You have to build name to match line from
modules.alias. But to match you have to put exact values for `dl' and `dh'.
Those values are simply not available when hotplug agent is called.

i.e. for the above line to match you have to supply exact values for vendor,
product, device low, device high. Any other values are not important but
these must be exact. But neither device low nor device high are known.

apparently the only way is to remove them and hope that usually the same
vendor/product combination is handled by single driver.

> So for your example, you would just:
> modprobe usb:v04E6p0006dl*dh*dc*dsc*dp*ic*isc*ip*

that won't match, sorry. wildcards can be in aliases; they can't be in module


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:58    [W:0.111 / U:0.060 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site