From: Marcus Harnisch <marcus.harnisch@gmx.net>
To: linux-hotplug@vger.kernel.org
Subject: Question about bcdDevice_(lo|hi)
Date: Wed, 09 Jan 2002 04:47:27 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-101055170808520@msgid-missing> (raw)
Hi List,
I just started to use linux hotplug (2001_09_19). When I tried to find
the reason why no map-entry for my camcorder matches, I came across
something I really don't understand.
usb.agent matches the bcdDevice columns in a map file using the
following statements:
: bcdDevice range $bcdDevice_hi $bcdDevice_lo actual $usb_bcdDevice
if [ $USB_MATCH_DEV_LO -eq $(( $match_flags & $USB_MATCH_DEV_LO )) ] &&
[ $usb_bcdDevice -lt $bcdDevice_lo ]; then
continue
fi
# bcdDevice_lo <= bcdDevice < bcdDevice_hi
if [ $USB_MATCH_DEV_HI -eq $(( $match_flags & $USB_MATCH_DEV_HI )) ] &&
[ $usb_bcdDevice -ge $bcdDevice_hi ]; then
continue
fi
The according entries in the map-files for all devices are a 4-digit
hexnumber for bcdDevice_lo and a 2-digit hexnumber for
bcdDevice_hi. With *very* few exceptions if bcdDevice that is greater
or equal to bcdDevice_lo (first condition) it is also greater than
bcdDevice_hi. This causes no match to be found in the vast majority of
cases (Þvices).
In my particular case, bcdDevice is 0x0300. So for test purposes I set
up an entry in usb.usermap with bcdDevice_lo to 0x0300. Which 2-digit
hexnumber would match the second condition? When I set bcdDevice_hi to
any number (well, I didn't try all of 'em :) above 0x02ff, everything
worked fine.
I really can't believe that this is a bug that nobody has seen
before. Can somebody explain that to me?
Best regards,
Marcus
_______________________________________________
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 reply other threads:[~2002-01-09 4:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 4:47 Marcus Harnisch [this message]
2002-01-11 20:55 ` Question about bcdDevice_(lo|hi) David Brownell
2002-01-12 2:42 ` Marcus Harnisch
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-101055170808520@msgid-missing \
--to=marcus.harnisch@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.