From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: file2alias - incorrect? aliases for USB
Date: Mon, 17 Nov 2003 18:11:28 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106909318904730@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106840503223499@msgid-missing>
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
names.
-andrey
-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2003-11-17 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-09 18:55 file2alias - incorrect? aliases for USB Andrey Borzenkov
2003-11-10 9:37 ` Greg KH
2003-11-14 1:02 ` Greg KH
2003-11-17 3:09 ` Rusty Russell
2003-11-17 18:11 ` Andrey Borzenkov [this message]
2003-12-11 9:29 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-11-17 6:24 "Andrey Borzenkov"
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-106909318904730@msgid-missing \
--to=arvidjaar@mail.ru \
--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).