linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fumitoshi UKAI <ukai@debian.or.jp>
To: linux-hotplug@vger.kernel.org
Subject: Forward: hotplugging usb-storage: bcdDevice at fault?
Date: Thu, 17 Jan 2002 16:22:17 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-101128461527545@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 709 bytes --]

Hi,

I received the attached mail from a user.  As he said, some entries have
bcdDevice_lo == bcdDevice_hi with match_flag & 0x0C == 0x0C, which means
matches for both device_lo and device_hi.  For examples, in 
drivers/usb/storage/unusual_devs.h:

UNUSUAL_DEV(  0x03f0, 0x0207, 0x0001, 0x0001,
                "HP",
                "CD-Writer+ 8200e",
                US_SC_8070, US_PR_SCM_ATAPI, init_8200e, 0),

But usb.agent code to match device_lo and device_hi is
bcdDevice_lo <= bcdDevice < bcdDevice_hi, so it is always fails
because bcdDevice_lo == bcdDevice_hi.

So, why usb.agent doesn't match bcdDevice_lo <= bcdDevice <=bcdDevice_hi?
Is it bugs of usb_device_id entries?

Thanks,
Fumitoshi UKAI


[-- Attachment #2: Type: message/rfc822, Size: 2619 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 1548 bytes --]

Dear Fumatoshi,

I'm having trouble getting hotplug to work with my HP 8230e CD Writer.  It's
a USB cdwriter, and works with the usb-storage module.  It works fine if I
modprobe usb-storage in by hand.

But hotplug doesn't recognise it, saying:
 /etc/hotplug/usb.agent: ... no modules for USB product 3f0/207/1

The entry for the device in /lib/modules/2.4.17/modules.usbmap is present,
and looks like
usb-storage          0x000f      0x03f0   0x0207    0x0001       0x0001
0x00         0x00            0x00            0x00            0x00
0x00               0x00000000

Watching the hotplug process carefully as it runs /etc/hotplug/usb.agent
when I plug the device in, I notice that it fails because bcdDevice_lo and
bcdDevice_hi are both set to 1, but the usb device (usb_bcdDevice) must
follow bcdDevice_lo <= bcdDevice < bcdDevice_hi.  That is, the module fails
to load because bcdDevice is not strictly less than bcdDevice_hi (all values
are equal to 1).

What does this mean?  What do I need to do to get it to run?  I notice that
your FinePix40i example in README.Debian:

usb-storage 0 0x04cb 0x0100 0x0000 0x0000 ...

also has bcdDevice_lo = bcdDevice_hi = 0,
and therefore ought to fail also for the same reason my cdwriter fails.  
Why does your camera succeed, while my cdwriter fails?

Thanks for any help you can provide.

Sincerely,

Drew Parsons

-- 
PGP public key available at http://people.debian.org/~dparsons/drewskey.txt
Fingerprint: A110 EAE1 D7D2 8076 5FE0  EC0A B6CE 7041 6412 4E4A

[-- Attachment #2.1.2: Type: application/pgp-signature, Size: 232 bytes --]

             reply	other threads:[~2002-01-17 16:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17 16:22 Fumitoshi UKAI [this message]
2002-01-17 20:22 ` Forward: hotplugging usb-storage: bcdDevice at fault? David Brownell
2002-01-18  3:10 ` Fumitoshi UKAI
2002-01-18  8:03 ` Matthew Dharm

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-101128461527545@msgid-missing \
    --to=ukai@debian.or.jp \
    --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).