From owner-freebsd-usb@FreeBSD.ORG  Mon May 23 08:47:42 2005
Return-Path: <owner-freebsd-usb@FreeBSD.ORG>
X-Original-To: freebsd-usb@freebsd.org
Delivered-To: freebsd-usb@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 67C2C16A41C
	for <freebsd-usb@freebsd.org>; Mon, 23 May 2005 08:47:42 +0000 (GMT)
	(envelope-from hselasky@c2i.net)
Received: from swip.net (mailfe09.tele2.se [212.247.155.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E503943D55
	for <freebsd-usb@freebsd.org>; Mon, 23 May 2005 08:47:38 +0000 (GMT)
	(envelope-from hselasky@c2i.net)
X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ==
Received: from mp-217-233-206.daxnet.no ([193.217.233.206] verified)
	by mailfe09.swip.net (CommuniGate Pro SMTP 4.3c5)
	with ESMTP id 163128397; Mon, 23 May 2005 10:47:17 +0200
From: Hans Petter Selasky <hselasky@c2i.net>
To: Daniel Rucci <rucci@warganizer.com>
Date: Mon, 23 May 2005 10:47:58 +0200
User-Agent: KMail/1.7
References: <428A2350.6000603@warganizer.com> <428F7723.8010102@elischer.org>
	<4291725C.50504@warganizer.com>
In-Reply-To: <4291725C.50504@warganizer.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200505231048.00554.hselasky@c2i.net>
Cc: Julian Elischer <julian@elischer.org>, freebsd-usb@freebsd.org,
	ticso@cicely.de
Subject: Re: force power over usb
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: hselasky@c2i.net
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2005 08:47:42 -0000

On Monday 23 May 2005 08:04, Daniel Rucci wrote:
>
>Standard Device Descriptor:
>  bLength            18
>  bDescriptorType    01
>  bcdUSB             0110
>  bDeviceClass       02
>  bDeviceSubClass    00
>  bDeviceProtocol    00
>  bMaxPacketSize     8
>  idVendor           22b8
>  idProduct          4902
>  bcdDevice          0001
>  iManufacturer      1
>  iProduct           2
>  iSerialNumber      0
>  bNumConfigurations 1
>
>Configuration 0:
>    Standard Configuration Descriptor:
>      bLength             9
>      bDescriptorType     02
>      wTotalLength        67
>      bNumInterface       2
>      bConfigurationValue 1
>      iConfiguration      4
>      bmAttributes        c0 (self-powered)
>      bMaxPower           50 (100 mA)

There is only one configuration, and that configuration is self-powered, so=
=20
I'm not sure if that cable is for charging. But do you know if it charges=20
under other OS'es ?

> =A0 =A0 Standard Interface Descriptor:
> =A0 =A0 =A0 bLength =A0 =A0 =A0 =A0 =A0 =A09
> =A0 =A0 =A0 bDescriptorType =A0 =A004
> =A0 =A0 =A0 bInterfaceNumber =A0 0
> =A0 =A0 =A0 bAlternateSetting =A00
> =A0 =A0 =A0 bNumEndpoints =A0 =A0 =A01
> =A0 =A0 =A0 bInterfaceClass =A0 =A002

bInterfaceClass is "CDC"=20

> =A0 =A0 =A0 bInterfaceSubClass 02

bInterfaceSubClass is "ABSTRACT_CONTROL_MODEL"

> =A0 =A0 =A0 bInterfaceProtocol 01
> =A0 =A0 =A0 iInterface =A0 =A0 =A0 =A0 5

according to defines in /sys/dev/usb/*

There is a spec available at:
http://www.usb.org/developers/devclass_docs/usbcdc11.pdf

But I'm not sure if it describes "bInterfaceProtocol 01".

What you can do is:

cat /dev/ugen0.1 | hexdump

Then do something on the phone and see what happens.

>    Standard Interface Descriptor:
>      bLength            9
>      bDescriptorType    04
>      bInterfaceNumber   1
>      bAlternateSetting  0
>      bNumEndpoints      2
>      bInterfaceClass    0a
>      bInterfaceSubClass 00
>      bInterfaceProtocol 00
>      iInterface         16

To get this interface working you will have to ask the vendor for informati=
on.=20
Maybe they've got a specification for it that is not propritary?

=2D-HPS