On Tue, 2010-02-16 at 22:36 -0800, Dan Williams wrote:
> On Tue, 2010-02-16 at 20:54 -0800, Greg KH wrote:
> > On Tue, Feb 16, 2010 at 06:39:26PM -0800, Dan Williams wrote:
> > > Hi,
> > >
> > > This short series adds some device IDs for CDMA/EVDO devices that are
> > > normally driven by CDC-ACM, but also provide an additional serial port
> > > that talks a proprietary Qualcomm protocol, QCDM. We now know enough of
> > > QCDM to start using these ports for radio status and signal strength
> > > when the CDC-ACM port is being used for PPP.
> >
> > Great, but how are we going to keep these devices from binding to the
> > cdc-acm module if it is loaded first? Do we need to blacklist them in
> > that driver at the same time?
>
> I don't think we care. The CDC-ACM part will be driven by cdc-acm, and
> the QCDM part gets driven by option.ko in parallel with the CDC-ACM.
> With these patches applied, you have both /dev/ttyACM0 (AT capable)
> and /dev/ttyUSB0 (QCDM capable). Somewhat like how the Ericsson "mbm"
> modems are concurrently driven by the cdc-wdm, cdc-ether, and cdc-acm
> class drivers all at the same time.
To clarify further, lsusb -v output from a CMOTECH CDX-650. The other
devices in the patch are similar.
Bus 007 Device 004: ID 16d8:6512 CMOTECH Co., Ltd.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x16d8 CMOTECH Co., Ltd.
idProduct 0x6512
bcdDevice 0.00
iManufacturer 1 CMOTECH CO., LTD.
iProduct 2 CMOTECH CDMA Technologies
iSerial 3 Serial Number
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 90
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
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.09
CDC Call Management:
bmCapabilities 0x03
call management
use DataInterface
bDataInterface 1
CDC ACM:
bmCapabilities 0x0f
connection notifications
sends break
line coding and serial state
get/set/clear comm features
CDC Union:
bMasterInterface 0
bSlaveInterface 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 32
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 4 Data Interface
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 0
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 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 0
iInterface 4 Data Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
