From: iSteve <isteve@rulez.cz>
To: "Randy.Dunlap" <rdunlap@xenotime.net>, linux-kernel@vger.kernel.org
Subject: Re: modules.isapnpmap vs modules.alias (now: modules.usbmap vs alias)
Date: Thu, 21 Sep 2006 16:54:24 +0200 [thread overview]
Message-ID: <20060921165424.139138e5@silver> (raw)
In-Reply-To: <20060920102248.ebb55960.rdunlap@xenotime.net>
On Wed, 20 Sep 2006 10:22:48 -0700
"Randy.Dunlap" <rdunlap@xenotime.net> wrote:
> It's defined in the MS ISA PNP spec from
> http://www.microsoft.com/whdc/resources/respec/specs/pnpisa.mspx
>
> I just went thru the bit fiddling exercise, so holler if you
> want/need help with it. (I'd rather just teach you how to fish
> instead of giving you fish.)
Mhm, thanks, I've got it... (also, I've found the fish itself;)
I've got one more question, this time regarding modules.usbmap.
-modules.usbmap:
ibmcam 0x000f 0x0545 0x8080 0x0002 0x0002 0x00 0x00 0x00 0x00 0x00 0x00 0x0
ibmcam 0x000f 0x0545 0x8080 0x030a 0x030a 0x00 0x00 0x00 0x00 0x00 0x00 0x0
ibmcam 0x000f 0x0545 0x8080 0x0301 0x0301 0x00 0x00 0x00 0x00 0x00 0x00 0x0
ibmcam 0x000f 0x0545 0x8002 0x030a 0x030a 0x00 0x00 0x00 0x00 0x00 0x00 0x0
ibmcam 0x000f 0x0545 0x800c 0x030a 0x030a 0x00 0x00 0x00 0x00 0x00 0x00 0x0
ibmcam 0x000f 0x0545 0x800d 0x030a 0x030a 0x00 0x00 0x00 0x00 0x00 0x00 0x0
-EOF
-With corresponding aliases:
alias usb:v0545p8080d0002dc*dsc*dp*ic*isc*ip* ibmcam
alias usb:v0545p8080d030[10-9]dc*dsc*dp*ic*isc*ip* ibmcam
alias usb:v0545p8080d0301dc*dsc*dp*ic*isc*ip* ibmcam
alias usb:v0545p8002d030[10-9]dc*dsc*dp*ic*isc*ip* ibmcam
alias usb:v0545p800Cd030[10-9]dc*dsc*dp*ic*isc*ip* ibmcam
alias usb:v0545p800Dd030[10-9]dc*dsc*dp*ic*isc*ip* ibmcam
-EOF
I absolutely do not understand the d030[10-9], where fields bcdDevice_lo and
bcdDevice_hi are 0x030a...
Looking at drivers/usb/core/usb.c, it'd seem that the MODALIAS sent upon device
event doesn't have anything like this -- it would have "[...]d030A[...]". So I
wonder, how it got generated?
-The relevant items in ibmcam.c:
static struct usb_device_id id_table[] = {
{ USB_DEVICE_VER(IBMCAM_VENDOR_ID, IBMCAM_PRODUCT_ID, 0x0002, 0x0002) },
{ USB_DEVICE_VER(IBMCAM_VENDOR_ID, IBMCAM_PRODUCT_ID, 0x030a, 0x030a) },
{ USB_DEVICE_VER(IBMCAM_VENDOR_ID, IBMCAM_PRODUCT_ID, 0x0301, 0x0301) },
{ USB_DEVICE_VER(IBMCAM_VENDOR_ID, NETCAM_PRODUCT_ID, 0x030a, 0x030a) },
{ USB_DEVICE_VER(IBMCAM_VENDOR_ID, VEO_800C_PRODUCT_ID, 0x030a, 0x030a) },
{ USB_DEVICE_VER(IBMCAM_VENDOR_ID, VEO_800D_PRODUCT_ID, 0x030a, 0x030a) },
{ }
};
-EOF
-And the resulting alias part of modinfo:
alias: usb:v0545p8080d0002dc*dsc*dp*ic*isc*ip*
alias: usb:v0545p8080d030[10-9]dc*dsc*dp*ic*isc*ip*
alias: usb:v0545p8080d0301dc*dsc*dp*ic*isc*ip*
alias: usb:v0545p8002d030[10-9]dc*dsc*dp*ic*isc*ip*
alias: usb:v0545p800Cd030[10-9]dc*dsc*dp*ic*isc*ip*
alias: usb:v0545p800Dd030[10-9]dc*dsc*dp*ic*isc*ip*
-EOF
Thanks in advance for any pointers
--
-- iSteve
next prev parent reply other threads:[~2006-09-21 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 16:53 modules.isapnpmap vs modules.alias iSteve
2006-09-20 17:22 ` Randy.Dunlap
2006-09-21 14:54 ` iSteve [this message]
2006-09-21 18:30 ` broken modules.alias entries for some USB devices Sergey Vlasov
2006-09-21 19:03 ` iSteve
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=20060921165424.139138e5@silver \
--to=isteve@rulez.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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