linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jian_yang@netzero.com
To: linux-hotplug@vger.kernel.org
Subject: why hotplug cannot support D-link DBT-120 driver problem?
Date: Mon, 12 May 2003 01:49:26 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-105270466131923@msgid-missing> (raw)


Hi every guy,
My linux operation system is Mandrake9.1, the kernel version is 2.4.21-0.13mdk. I install bluez-bluefw-1.0. The system can detect 3COM 3RCEB96 bluetooth usb adapter, but cannot detect D-link DBT-120. 

I check the log and cat /proc/bus/usb/devices;
They report:

hub.c: new USB device 00:07.2-2, assigned address 4
usb.c: USB device 4 (vend/prod 0xa5c/0x2033) is not claimed by any active driver.
                                                                                                                            
[root@mandrake1 usb]# cat /proc/bus/usb/devices
T:  Bus\x01 Lev\0 Prnt\0 Port\0 Cnt\0 Dev#=  1 Spd\x12  MxCh= 2
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 1.00 Cls	(hub  ) Sub\0 Prot\0 MxPS= 8 #Cfgs=  1
P:  Vendor\000 ProdID\000 Rev= 0.00
S:  Product=USB UHCI Root Hub
S:  SerialNumber‰00
C:* #Ifs= 1 Cfg#= 1 Atr@ MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls	(hub  ) Sub\0 Prot\0 Driver=hub
E:  AdÅ(I) Atr\x03(Int.) MxPS=   8 Ivl%5ms
T:  Bus\x01 Lev\x01 Prnt\x01 Port\x01 Cnt\x01 Dev#=  7 Spd\x12  MxCh= 0
D:  Ver= 1.01 Cls‡(unk. ) Sub\x01 Prot\x01 MxPSd #Cfgs=  1
P:  Vendor
5c ProdID 33 Rev= 0.a0
C:* #Ifs= 3 Cfg#= 1 Atr† MxPwr\x100mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls‡(unk. ) Sub\x01 Prot\x01 Driver=(none)
E:  AdÅ(I) Atr\x03(Int.) MxPS=  16 Ivl=1ms
E:  AdÇ(I) Atr\x02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad\x02(O) Atr\x02(Bulk) MxPS=  64 Ivl=0ms
I:  If#= 1 Alt= 0 #EPs= 2 Cls‡(unk. ) Sub\x01 Prot\x01 Driver=(none)
E:  AdÉ(I) Atr\x01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad\x03(O) Atr\x01(Isoc) MxPS=   0 Ivl=1ms
I:  If#= 1 Alt= 1 #EPs= 2 Cls‡(unk. ) Sub\x01 Prot\x01 Driver=(none)
E:  AdÉ(I) Atr\x01(Isoc) MxPS=  16 Ivl=1ms
E:  Ad\x03(O) Atr\x01(Isoc) MxPS=  16 Ivl=1ms
I:  If#= 1 Alt= 2 #EPs= 2 Cls‡(unk. ) Sub\x01 Prot\x01 Driver=(none)
E:  AdÉ(I) Atr\x01(Isoc) MxPS=  32 Ivl=1ms
E:  Ad\x03(O) Atr\x01(Isoc) MxPS=  32 Ivl=1ms
I:  If#= 1 Alt= 3 #EPs= 2 Cls‡(unk. ) Sub\x01 Prot\x01 Driver=(none)
E:  AdÉ(I) Atr\x01(Isoc) MxPS=  32 Ivl=1ms
E:  Ad\x03(O) Atr\x01(Isoc) MxPS=  32 Ivl=1ms
I:  If#= 1 Alt= 4 #EPs= 2 Cls‡(unk. ) Sub\x01 Prot\x01 Driver=(none)
E:  AdÉ(I) Atr\x01(Isoc) MxPS=  64 Ivl=1ms
E:  Ad\x03(O) Atr\x01(Isoc) MxPS=  64 Ivl=1ms

if I use
bluefw usb 001/004,
every thing is ok.

I read the document about hotplug, but I still have no idea what I can do.

If anyone can give me some advice, I will be grateful.

Thank you very much

Jian Yang



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
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

                 reply	other threads:[~2003-05-12  1:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-105270466131923@msgid-missing \
    --to=jian_yang@netzero.com \
    --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).