* How to add new CDC-ACM usb modem device to supported list?
@ 2009-01-26 10:47 Ed W
2009-01-26 11:21 ` Ed W
2009-01-26 11:49 ` Oliver Neukum
0 siblings, 2 replies; 4+ messages in thread
From: Ed W @ 2009-01-26 10:47 UTC (permalink / raw)
To: linux-kernel
Hi, I have a wireless modem device which I believe to be a normal usb
ACM modem type device (works this way in windows where there is just a
.inf file supplied which connects the device with usbser.sys). I'm not
quite sure how to get the 2.6 kernel to notice and connect the acm
driver to this device though? I have poked through the code in
./drivers/usb/class/ and can't immediately spot how to add unsupported
USB devices to be detected? I also read the cdc-acm kernel readme and
have a rough idea on what should be happening
Could someone please point me in the correct direction? (Grateful for a
CC offlist)
Ed W
Relevant section from lsusb
Bus 006 Device 004: ID 1edd:9555
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 32
idVendor 0x1edd
idProduct 0x9555
bcdDevice 0.00
iManufacturer 1 Iridium
iProduct 2 Iridium 9555 Handset
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 62
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 250mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 0
CDC Header:
bcdCDC 1.10
CDC ACM:
bmCapabilities 0x07
sends break
line coding and serial state
get/set/clear comm features
CDC Call Management:
bmCapabilities 0x03
call management
use DataInterface
bDataInterface 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Device Status: 0x0001
Self Powered
Bus 006 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.22.19-grsec2.1.11-vs2.2.0.7 uhci_hcd
iProduct 2 UHCI Host Controller
iSerial 1 0000:00:1d.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
bPwrOn2PwrGood 1 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0103 power enable connect
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled
Relevant bits from /proc/bus/usb/devices
T: Bus=06 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.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.22.19-grsec2.1.11-vs2.2.0.7 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 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= 2 Ivl=255ms
T: Bus=06 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=32 #Cfgs= 1
P: Vendor=1edd ProdID=9555 Rev= 0.00
S: Manufacturer=Iridium
S: Product=Iridium 9555 Handset
C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr=250mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=01 Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=1ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=(none)
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to add new CDC-ACM usb modem device to supported list?
2009-01-26 10:47 How to add new CDC-ACM usb modem device to supported list? Ed W
@ 2009-01-26 11:21 ` Ed W
2009-01-26 12:00 ` Oliver Neukum
2009-01-26 11:49 ` Oliver Neukum
1 sibling, 1 reply; 4+ messages in thread
From: Ed W @ 2009-01-26 11:21 UTC (permalink / raw)
To: linux-kernel
Ed W wrote:
> Hi, I have a wireless modem device which I believe to be a normal usb
> ACM modem type device (works this way in windows where there is just a
> .inf file supplied which connects the device with usbser.sys).
...
> I also read the cdc-acm kernel readme and
> have a rough idea on what should be happening
>
>
After fixing an embarrassingly trivial configuration error, the acm
driver *is* in fact loading correctly...
However, I'm not getting any response using either minicom or "cu". I
suspect something fairly simple - can someone perhaps point me towards
how to get some more detailed debugging info from this kind of USB
device please?
Relevant bits from /proc/bus/usb/devices
T: Bus=06 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.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.22.19-grsec2.1.11-vs2.2.0.7 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 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= 2 Ivl=255ms
T: Bus=06 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 8 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=32 #Cfgs= 1
P: Vendor=1edd ProdID=9555 Rev= 0.00
S: Manufacturer=Iridium
S: Product=Iridium 9555 Handset
C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr=250mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=01 Driver=cdc_acm
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=1ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
dmesg
[5075781.727325] usb 6-2: new full speed USB device using uhci_hcd and
address 8
[5075781.911917] usb 6-2: configuration #1 chosen from 1 choice
[5075781.915864] hci_usb: probe of 6-2:1.0 failed with error -5
[5075781.915879] cdc_acm 6-2:1.0: ttyACM0: USB ACM device
Presumably this error -5 is relevant??
Thanks
Ed W
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to add new CDC-ACM usb modem device to supported list?
2009-01-26 10:47 How to add new CDC-ACM usb modem device to supported list? Ed W
2009-01-26 11:21 ` Ed W
@ 2009-01-26 11:49 ` Oliver Neukum
1 sibling, 0 replies; 4+ messages in thread
From: Oliver Neukum @ 2009-01-26 11:49 UTC (permalink / raw)
To: Ed W, linux-usb; +Cc: linux-kernel
Am Monday 26 January 2009 11:47:28 schrieb Ed W:
> Hi, I have a wireless modem device which I believe to be a normal usb
> ACM modem type device (works this way in windows where there is just a
> .inf file supplied which connects the device with usbser.sys). I'm not
> quite sure how to get the 2.6 kernel to notice and connect the acm
> driver to this device though? I have poked through the code in
It should be detected as is. Please provide dmesg.
Regards
Oliver
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to add new CDC-ACM usb modem device to supported list?
2009-01-26 11:21 ` Ed W
@ 2009-01-26 12:00 ` Oliver Neukum
0 siblings, 0 replies; 4+ messages in thread
From: Oliver Neukum @ 2009-01-26 12:00 UTC (permalink / raw)
To: Ed W, linux-usb; +Cc: linux-kernel
Am Monday 26 January 2009 12:21:18 schrieb Ed W:
> dmesg
> [5075781.727325] usb 6-2: new full speed USB device using uhci_hcd and
> address 8
> [5075781.911917] usb 6-2: configuration #1 chosen from 1 choice
> [5075781.915864] hci_usb: probe of 6-2:1.0 failed with error -5
> [5075781.915879] cdc_acm 6-2:1.0: ttyACM0: USB ACM device
>
>
> Presumably this error -5 is relevant??
That is from hci_usb, the old bluetooth dongle driver. Why this probes your
device I don't know, but it should work anyway. The cdc-acm driver can
be compiled with extra debugging. It has the lines:
#undef DEBUG
#undef VERBOSE_DEBUG
If you replace #undef with #define you get more debugging output.
Regards
Oliver
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-01-26 12:00 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-01-26 10:47 How to add new CDC-ACM usb modem device to supported list? Ed W
2009-01-26 11:21 ` Ed W
2009-01-26 12:00 ` Oliver Neukum
2009-01-26 11:49 ` Oliver Neukum
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).