AJZaurusUSB

Issue 79: Attempting to use AJZaurusUSB with HTC Desire

Reported by Matt Holgate, May 14, 2010

I thought I'd have a go attempting to use AJZaurusUSB with my HTC 
Desire Android phone, on Snow Leopard. I added the product/vendor ID 
stuff to the plist, but the driver does not work.

I suspect this is because the device uses RNDIS (but also has a 
'Data' interface - bInterfaceClass = 10).

I've pasted the output of dmesg below, and I suspect there is no 
chance of getting this working, but I thought I'd ask in case I've 
misunderstood and there is something I can do.

Many thanks!

AJZaurusUSB::start - this=0x41a3000 provider=0x454e200
AJZaurusUSB::createWorkLoop - thread=0x600a000 workLoop=0x50ab480
AJZaurusUSB::getWorkLoop (0x50ab480)
AJZaurusUSB::createOutputQueue
AJZaurusUSB::configureDevice 1 configs
AJZaurusUSB::dumpDevice - Enumerating 1 configurations ...
AJZaurusUSB::dumpDevice - Enumerate Configuration: 0
AJZaurusUSB::dumpDevive -   Interface 0[0] found
AJZaurusUSB::dumpDevice -     bLength=9
AJZaurusUSB::dumpDevice -     bDescriptorType=4
AJZaurusUSB::dumpDevice -     bInterfaceNumber=0
AJZaurusUSB::dumpDevice -     bInterfaceClass=2
AJZaurusUSB::dumpDevice -     bInterfaceSubClass=2
AJZaurusUSB::dumpDevice -     bInterfaceProtocol=255
AJZaurusUSB::dumpDevice -     bAlternateSetting=0
AJZaurusUSB::dumpDevice -     bNumEndpoints=1
AJZaurusUSB::dumpDevice -     iInterface=6
AJZaurusUSB::dumpDevive -   Interface 1[0] found
AJZaurusUSB::dumpDevice -     bLength=9
AJZaurusUSB::dumpDevice -     bDescriptorType=4
AJZaurusUSB::dumpDevice -     bInterfaceNumber=1
AJZaurusUSB::dumpDevice -     bInterfaceClass=10
AJZaurusUSB::dumpDevice -     bInterfaceSubClass=0
AJZaurusUSB::dumpDevice -     bInterfaceProtocol=0
AJZaurusUSB::dumpDevice -     bAlternateSetting=0
AJZaurusUSB::dumpDevice -     bNumEndpoints=2
AJZaurusUSB::dumpDevice -     iInterface=6
AJZaurusUSB::configureDevice - Checking Configuration 0
AJZaurusUSB::configureDevice -   matching Interface descriptor 
found: 1
AJZaurusUSB::message - type 3758096641/e0000101 provider=0x454e200 
argument=0
AJZaurusUSB::message - kIOMessageServiceAttemptingOpen
AJZaurusUSB::message - type 3758096641/e0000101 provider=0x454e200 
argument=0
AJZaurusUSB::message - kIOMessageServiceAttemptingOpen
       0        0 AppleUSBCDCACMControl: start - Failed to find the 
CDC driver
       0        1 AppleUSBCDCACMData: start - Find CDC driver for 
data interface failed
AJZaurusUSB::configureDevice -    bmAttributes=00000080
AJZaurusUSB::configureDevice -   InterfaceClass=2
AJZaurusUSB::configureDevice -   InterfaceSubClass=2
AJZaurusUSB::configureDevice -   InterfaceProtocol=255
AJZaurusUSB::configureDevice -   InterfaceClass=10
AJZaurusUSB::configureDevice -   InterfaceSubClass=0
AJZaurusUSB::configureDevice -   InterfaceProtocol=0
AJZaurusUSB::configureDevice -   no matching interface for 
configuration 0
AJZaurusUSB::configureDevice -  no matching Interface descriptor 
found
AJZaurusUSB::start - configure Device failed
AJZaurusUSB::stop
AJZaurusUSB::free

Comment 1 by Nikolaus Schaller, Jun 26, 2010

This indicates that the HTC is not a CDC Ethernet gadget compatible 
device. And AJZaurusUSB does not support RNDIS. So it simply can not 
work unless deep analysis of the protocols provided by the HTC 
device are provided.
Status: WontFix

Created: 14 years 1 month ago by Matt Holgate

Updated: 14 years 17 days ago

Status: WontFix

Followed by: 1 person

Labels:
Type:Defect
Priority:Medium