On Tue, May 3, 2011 at 16:13, Stuart Henderson <s...@spacehopper.org> wrote:

> vovka <net.vlad <at> gmail.com> writes:
> > On Sat, Apr 30, 2011 at 18:08, Erik Mugele <ejm <at> teuton.org> wrote:
> > > The following patch against -current enables the Samsung Galaxy S
> > > Android device (Samsung Captivate with AT&T) to be be used for USB
> > > tethering.
> >      Erik, great work and great patch... I, too, have a Samsung Galaxy S.
> > Your patch did not apply correctly, so here is my version of it.I've also
> > attached a diff of "usbdevs.h" .
>
> Please pkg_add usbutil, then identify the relevant /dev/usbX controller
> device (from "usbdevs -v" output), run "usbctl -f /dev/usbX", and include
> the output. If other people with different Android phones that support
> this mode of tethering could do the same, we may be able to identify
> a suitable class id we can match on instead.
>
>
This, of course, may be slightly of topic, but upon attaching a T-mobile G1
(HTC Dream) in attempt to use USB TETHER,
everything works without and further 'tinkering'

umass1 at uhub0 port 1 configuration 1 interface 0 "HTC Android Phone" rev
2.00/2.27 addr 3
umass1: using SCSI over Bulk-Only
scsibus5 at umass1: 2 targets, initiator 0
sd4 at scsibus5 targ 1 lun 0: <HTC, Android Phone, 0100> SCSI2 0/direct
removable serial.0bb40c02HT93JLD03777
ugen1 at uhub0 port 1 configuration 1 "HTC Android Phone" rev 2.00/2.27 addr
3
sd4 detached
scsibus5 detached
umass1 detached
ugen1 detached
urndis0 at uhub0 port 1 configuration 1 interface 0 "HTC Android Phone" rev
2.00/2.27 addr 3
urndis0: address b2:6d:ca:3c:e2:e6
ugen1 at uhub0 port 1 configuration 1 "HTC Android Phone" rev 2.00/2.27 addr
3

Output of 'usbctl -f /dev/usbX' :

Controller /dev/usb0:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000),
Intel(0x8086), rev 1.00
 port 1 addr 3: high speed, self powered, config 1, Android Phone(0x0ffc),
HTC(0x0bb4), rev 2.27, iSerialNumber HT93JLD03777

DEVICE addr 3
DEVICE descriptor:
bLength=18 bDescriptorType=device(1) bcdUSB=2.00 bDeviceClass=224
bDeviceSubClass=0
bDeviceProtocol=0 bMaxPacketSize=64 idVendor=0x0bb4 idProduct=0x0ffc
bcdDevice=227
iManufacturer=1(HTC) iProduct=2(Android Phone) iSerialNumber=3(HT93JLD03777)
bNumConfigurations=1

CONFIGURATION descriptor 0:
bLength=9 bDescriptorType=config(2) wTotalLength=98 bNumInterface=3
bConfigurationValue=1 iConfiguration=0() bmAttributes=c0 bMaxPower=500 mA

Unknown descriptor (class 224/0):
bLength=8 bDescriptorType=11 ...

INTERFACE descriptor 0:
bLength=9 bDescriptorType=interface(4) bInterfaceNumber=0
bAlternateSetting=0
bNumEndpoints=1 bInterfaceClass=224 bInterfaceSubClass=1
bInterfaceProtocol=3 iInterface=4(RNDIS Communications Control)

Unknown descriptor (class 224/1):
bLength=5 bDescriptorType=36 ...

Unknown descriptor (class 224/1):
bLength=5 bDescriptorType=36 ...

Unknown descriptor (class 224/1):
bLength=4 bDescriptorType=36 ...

Unknown descriptor (class 224/1):
bLength=5 bDescriptorType=36 ...

ENDPOINT descriptor:
bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=2-in
bmAttributes=interrupt wMaxPacketSize=8 bInterval=9

INTERFACE descriptor 1:
bLength=9 bDescriptorType=interface(4) bInterfaceNumber=1
bAlternateSetting=0
bNumEndpoints=2 bInterfaceClass=10 bInterfaceSubClass=0
bInterfaceProtocol=0 iInterface=5(RNDIS Ethernet Data)

ENDPOINT descriptor:
bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=1-in
bmAttributes=bulk wMaxPacketSize=512 bInterval=0

ENDPOINT descriptor:
bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=1-out
bmAttributes=bulk wMaxPacketSize=512 bInterval=0

INTERFACE descriptor 2:
bLength=9 bDescriptorType=interface(4) bInterfaceNumber=2
bAlternateSetting=0
bNumEndpoints=2 bInterfaceClass=255 bInterfaceSubClass=66
bInterfaceProtocol=1 iInterface=0()

ENDPOINT descriptor:
bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=4-in
bmAttributes=bulk wMaxPacketSize=512 bInterval=0

ENDPOINT descriptor:
bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=3-out
bmAttributes=bulk wMaxPacketSize=512 bInterval=0

current configuration 1

----------

Reply via email to