When connecting a Vodafone 715 mobile phone to a PC running Ubuntu Gutsy...nothing happens. Well, nothing visible. lsusb reveals that the kernel sees the device plugged in:
$ lsusb
Bus 003 Device 005: ID 12d1:1009
The phone is a rebadged Huawei U120. I believe that it should support
mass-storage, CDC modem and SyncML using OBEX over USB.
Googling for 12d1 reveals that indeed 12d1 is the vendor ID for Huawei.
However, linux-usb.org has only the following entries:
12d1 Huawei Technologies Co., Ltd.
1001 E620 USB Modem
1003 E220 HSDPA Modem
No obvious support for model U120.
Is it practical to roll-your-own support for an unsupported device? In
the days of hotplug, I knew where to start typing. But I have not really
followed the transition to udev, HAL and all its friends.
Just USB mass-storage support (to speed up transfer of files to the
device) would be enough: it costs too much to access the internet via
mobile phone.
Bluetooth works just fine: pairing was easy, files transfer in both
directions (but slowly), and synchronisation with Evolution address
books using opensync is good.
Is there enough data in lsusb -v to determine exactly which protocols
the device support? On Bluetooth, sdptool tells you what the remove
device can do.
Those vendor specific protocol class, subclass and protocol worry me
somewhat.
Any pointers would be greatly appreciated.
$ lsusb -v
Bus 003 Device 005: ID 12d1:1009
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x12d1
idProduct 0x1009
bcdDevice 0.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 62
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 128
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 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 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 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Thanks
Stephen Irons
=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
=======================================================================
file:///C:/DOCUME~1/IRONSS/LOCALS~1/TEMP/nsmail.tmp
Description: PGP signature
