From owner-freebsd-usb@FreeBSD.ORG  Wed Sep  8 07:55:23 2010
Return-Path: <owner-freebsd-usb@FreeBSD.ORG>
Delivered-To: freebsd-usb@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 11EBB10656C1
	for <freebsd-usb@freebsd.org>; Wed,  8 Sep 2010 07:55:23 +0000 (UTC)
	(envelope-from nick@van-laarhoven.org)
Received: from cpsmtpb-ews05.kpnxchange.com (cpsmtpb-ews05.kpnxchange.com
	[213.75.39.8]) by mx1.freebsd.org (Postfix) with ESMTP id 8DD5B8FC08
	for <freebsd-usb@freebsd.org>; Wed,  8 Sep 2010 07:55:21 +0000 (UTC)
Received: from cpbrm-ews04.kpnxchange.com ([10.94.84.135]) by
	cpsmtpb-ews05.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.4675); 
	Wed, 8 Sep 2010 09:55:20 +0200
Received: from CPSMTPM-EML102.kpnxchange.com ([195.121.3.6]) by
	cpbrm-ews04.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.4675); 
	Wed, 8 Sep 2010 09:55:21 +0200
Received: from uitsmijter.van-laarhoven.org ([81.207.207.222]) by
	CPSMTPM-EML102.kpnxchange.com with Microsoft
	SMTPSVC(7.0.6002.18222); Wed, 8 Sep 2010 09:55:19 +0200
Received: from static.kpn.net (static.kpn.net [92.69.105.40] (may be forged))
	(authenticated bits=0)
	by uitsmijter.van-laarhoven.org (8.14.4/8.14.4) with ESMTP id
	o887tGaK048735; Wed, 8 Sep 2010 09:55:17 +0200 (CEST)
	(envelope-from nick@van-laarhoven.org)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Nick Hibma <nick@van-laarhoven.org>
In-Reply-To: <201009080900.46802.hselasky@c2i.net>
Date: Wed, 8 Sep 2010 09:51:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <598B1BC2-3B47-4188-A637-1831C49477B3@van-laarhoven.org>
References: <43EC7D78-31E5-4B86-9316-002AE650727A@tlb.org>
	<20100505121841.ce3cf358.ray@dlink.ua>
	<03EA4629-81F5-442C-9064-95E1A265D8AD@van-laarhoven.org>
	<201009080900.46802.hselasky@c2i.net>
To: Hans Petter Selasky <hselasky@c2i.net>
X-Mailer: Apple Mail (2.1081)
X-Spam-Status: No, score=-8.9 required=5.0 tests=J_CHICKENPOX_12, MAY_BE_FORGED,
	MR_DIFF_MID,MR_NOT_ATTRIBUTED_IP,RCVD_IN_PBL,TW_MK,USER_IN_WHITELIST,
	USER_IN_WHITELIST_TO autolearn=no version=3.3.0
X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on
	uitsmijter.van-laarhoven.org
X-OriginalArrivalTime: 08 Sep 2010 07:55:19.0885 (UTC)
	FILETIME=[2EE097D0:01CB4F2B]
X-RcptDomain: freebsd.org
Cc: freebsd-usb@freebsd.org
Subject: Re: USB serial device naming
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
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: Wed, 08 Sep 2010 07:55:23 -0000

>> Two things are needed:
>>=20
>> 1) path to the device so you can distinguish two identical devices.
>>=20
>> 2) map u3gN to cuaUX.Y
>>=20
>> My problem is the latter:
>>=20
>> Processing event '+u3g0 vendor=3D0x0af0 product=3D0x7601 =
devclass=3D0xff
>> devsubclass=3D0xff sernum=3D"" release=3D0x0000 intclass=3D0xff =
intsubclass=3D0xff
>> at port=3D2 interface=3D0 vendor=3D0x0af0 product=3D0x7601 =
devclass=3D0xff
>> devsubclass=3D0xff sernum=3D"" release=3D0x0000 intclass=3D0xff =
intsubclass=3D0xff
>> on uhub1' Pushing table
>=20
> Hi,
>=20
>> How do I get to the cuaU10.0 device here? As far as I can see there =
is no
>> way to do this.
>=20
> I think we should use the following format:
>=20
> cuaU<bus>.<addr>.<iface>[.<sub_unit>]
>=20
> Then you can match by ugenX.Y unit. Possibly we could add this =
information to=20
> the processing event.

Yes. We need a mapping from vendor/product/rev -> /dev/ entry and from =
location -> /dev/ entry. Adding this cuaU<bus>.<addr>.<iface> string =
(not the absence of the sub_unit) to the event would resolve both issues =
1) and 2).

/me starts handing out paint and pencils for the bike shed painting to =
come...

>> The main problem is the strange way the minor number is assigned to =
the
>> cuaU device. But having the major and minor numbers for the cuaU =
device
>> per u3g instance would be sufficient. Through a sysctl for example, =
or as
>> extra information in the attach.
>=20
> You mean in the device name, not in the inode?

Device name, right. The mknod stuff is too old to be wrong...

> Please send a patch for review.

Will do in the next two weeks.

Nick=