Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 5 May 2010 09:52:15 +0200
From:      Hans Petter Selasky <hselasky@c2i.net>
To:        Mike Tancsa <mike@sentex.net>
Cc:        Andrew Thompson <thompsa@freebsd.org>, freebsd-usb@freebsd.org
Subject:   Re: USB serial device naming
Message-ID:  <201005050952.15632.hselasky@c2i.net>
In-Reply-To: <201005042027.o44KRete011712@lava.sentex.ca>
References:  <43EC7D78-31E5-4B86-9316-002AE650727A@tlb.org> <200912140948.08171.hselasky@c2i.net> <201005042027.o44KRete011712@lava.sentex.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

Maybe you can make PR on the issue and assign it to USB. Currently there is no 
way of knowing which /dev/cuaUXXX belongs to which USB device. Probably we can 
add the USB bus and address number as a part of the device coordinates. So 
that /dev/ugen1.1 only creates /dev/cuaU1.1.xxx entries. And then we can also 
remove the current unit number allocation structure I guess, if we use:

/dev/cuaU1.1.<iface_number>.<optional_sub_modem_unit>

The only problem is: Will we break any existing applications?

The second problem was that the USB attach event was generated before the 
modem was probed and the umodem and other modem drivers do not provide any 
information about their USB address in the pnpinfo. This can be fixed.

Old pnpinfo:

dev.ums.0.%pnpinfo: vendor=0x0 product=0x0 devclass=0x00 devsubclass=0x00 
sernum="" release=0x0200 intclass=0x03 intsubclass=0x01

Suggested new pnpinfo (which is available from devd.conf I guess)

dev.ums.0.%pnpinfo: vendor=0x0 product=0x0 devclass=0x00 devsubclass=0x00 
sernum="" release=0x0200 intclass=0x03 intsubclass=0x01 bus=1 addr=2 
ifaceidx=0

What do you think?

--HPS



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201005050952.15632.hselasky>