Hi folks, My system information Redhat 7.1 and kernel 2.4.9-6.
I have a USB Bluetooth chip, Transilica Evaluation Kit http://www.transilica.com/prod.html , the smallest Bluetooth SOC( system on chip) product. The device is working fine in the Windows environment and standalone. We could not even able to initialize the device. I suspect its class/subclass/protocol numbers might differ from the "usual" ones (0xe0/0x01/0x01). I have tried out to include the usbfs into the kernel and enabled experimental USB device filesystem support in the kernel and mount it as follows: mount -t usbdevfs none /proc/bus/usb but I found that the Transilica device uses the "normal number". The traces are shown here: #After USB is plugged into the the Transilica Evaluation Kit 1700 or 1760 #The following messages are recorded in the /proc/bus/USB/devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=ef80 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms #The following messages are recorded in the /proc/bus/usb/drivers usbdevfs hub hci_usb #The kernel trace is shown here: Dec 13 19:16:08 desktop12 kernel: usb-uhci.c: $Revision: 1.259 $ time 19:49:50 Nov 22 2001 Dec 13 19:16:08 desktop12 kernel: usb-uhci.c: High bandwidth mode enabled Dec 13 19:16:08 desktop12 kernel: PCI: Found IRQ 10 for device 00:1f.2 Dec 13 19:16:08 desktop12 kernel: PCI: Setting latency timer of device 00:1f.2 to 64 Dec 13 19:16:08 desktop12 kernel: usb-uhci.c: USB UHCI at I/O 0xef80, IRQ 10 Dec 13 19:16:08 desktop12 kernel: usb-uhci.c: Detected 2 ports Dec 13 19:16:08 desktop12 kernel: usb.c: new USB bus registered, assigned bus number 1 Dec 13 19:16:08 desktop12 kernel: Product: USB UHCI Root Hub Dec 13 19:16:08 desktop12 kernel: SerialNumber: ef80 Dec 13 19:16:08 desktop12 kernel: hub.c: USB hub found Dec 13 19:16:08 desktop12 kernel: hub.c: 2 ports detected Dec 13 19:16:08 desktop12 kernel: usb-uhci.c: v1.251:USB Universal Host Controller Interface driver Dec 13 19:16:08 desktop12 /sbin/hotplug: arguments (usb) env (PWD=/etc/hotplug HOSTNAME=desktop12 DEVICE=/proc/bus/usb/001/001 ACTION=add DEBUG=kernel MACHTYPE=i386-redhat-linux-gnu OLDPWD=/ DEVFS=/proc/bus/usb TYPE=9/0/0 SHLVL=1 SHELL=/bin/bash HOSTTYPE=i386 OSTYPE=linux-gnu HOME=/ TERM=dumb PATH=/bin:/sbin:/usr/sbin:/usr/bin PRODUCT=0/0/0 _=/usr/bin/env) Dec 13 19:16:08 desktop12 /sbin/hotplug: invoke /etc/hotplug/usb.agent Dec 13 19:16:08 desktop12 /etc/hotplug/usb.agent: ... no drivers for USB product 0/0/0 Dec 13 19:16:09 desktop12 kernel: hub.c: USB new device connect on bus1/2, assigned device number 2 Dec 13 19:16:09 desktop12 kernel: usb-uhci.c: interrupt, status 2, frame# 702 Dec 13 19:16:09 desktop12 kernel: usb.c: USB device not accepting new address=2 (error=-110) Dec 13 19:16:09 desktop12 kernel: hub.c: USB new device connect on bus1/2, assigned device number 3 Dec 13 19:16:09 desktop12 kernel: usb-uhci.c: interrupt, status 2, frame# 952 Dec 13 19:16:09 desktop12 kernel: usb.c: USB device not accepting new address=3 (error=-110) Dec 13 19:16:19 desktop12 kernel: BlueZ HCI Core ver 2.0 Copyright (C) 2000,2001 Qualcomm Inc Dec 13 19:16:19 desktop12 kernel: Written 2000,2001 by Maxim Krasnyansky <[EMAIL PROTECTED]> Dec 13 19:16:19 desktop12 kernel: BlueZ HCI USB driver ver 2.0 Copyright (C) 2000,2001 Qualcomm Inc Dec 13 19:16:19 desktop12 kernel: Written 2000,2001 by Maxim Krasnyansky <[EMAIL PROTECTED]> Dec 13 19:16:19 desktop12 kernel: usb.c: registered new driver hci_usb Dec 13 19:16:43 desktop12 kernel: hub.c: USB new device connect on bus1/2, assigned device number 4 Dec 13 19:16:43 desktop12 kernel: usb-uhci.c: interrupt, status 2, frame# 1860 Dec 13 19:16:43 desktop12 kernel: usb.c: USB device not accepting new address=4 (error=-110) Dec 13 19:16:43 desktop12 kernel: hub.c: USB new device connect on bus1/2, assigned device number 5 Dec 13 19:16:43 desktop12 kernel: usb-uhci.c: interrupt, status 2, frame# 62 Dec 13 19:16:43 desktop12 kernel: usb.c: USB device not accepting new address=5 (error=-110) #I also test the USB out with The Ericsson Bluetooth two module Kit. It is working fine and gives the massages in /proc/bus/usb/devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=ef80 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS= 8 #Cfgs= 1 P: Vendor=08ea ProdID=abba Rev= 0.01 S: Manufacturer=Ericsson S: Product=Bluetooth Device C:* #Ifs= 3 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=04(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=85(I) Atr=03(Int.) MxPS= 16 Ivl= 1ms I: If#= 1 Alt= 0 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb E: Ad=81(I) Atr=01(Isoc) MxPS= 0 Ivl= 1ms E: Ad=02(O) Atr=01(Isoc) MxPS= 0 Ivl= 1ms I: If#= 1 Alt= 1 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb E: Ad=81(I) Atr=01(Isoc) MxPS= 9 Ivl= 1ms E: Ad=02(O) Atr=01(Isoc) MxPS= 9 Ivl= 1ms I: If#= 1 Alt= 2 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb E: Ad=81(I) Atr=01(Isoc) MxPS= 17 Ivl= 1ms E: Ad=02(O) Atr=01(Isoc) MxPS= 17 Ivl= 1ms I: If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none) Here are my questions: Could anyone please tell me what Error (-100) is? It seems that the transilica bluetooth kit is not supported by the Linux USB (either uhci, usb-uhci and usb-ohci, also bluetooth.o) driver. If anyone want to help me include this device into the Linux usb driver, what are the information I need to provide? I guess it has nothing to do with the blutooth in this stage,right? If I want to customize the USB driver include in the kernel to include my driver, where should I look into? Thanks. Best regards, Xiaoyong _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
