From owner-freebsd-usb@FreeBSD.ORG Wed Feb 4 10:24:55 2009 Return-Path: Delivered-To: usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C46371065677; Wed, 4 Feb 2009 10:24:55 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.swip.net [212.247.154.161]) by mx1.freebsd.org (Postfix) with ESMTP id 2C1F38FC25; Wed, 4 Feb 2009 10:24:54 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=yeonV4BSZWp0Uy9YbVcA:9 a=ZAKByqpdGbYrO5BrN7gncJwTxGYA:4 a=LY0hPdMaydYA:10 Received: from [85.19.218.115] (account mc467741@c2i.net HELO [10.37.1.92]) by mailfe06.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1191396970; Wed, 04 Feb 2009 11:24:53 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org, vova@fbsd.ru Date: Wed, 4 Feb 2009 11:27:19 +0100 User-Agent: KMail/1.9.7 References: <1233734352.1767.55.camel@localhost> <200902041044.27663.hselasky@c2i.net> <1233741482.1767.120.camel@localhost> In-Reply-To: <1233741482.1767.120.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902041127.20424.hselasky@c2i.net> Cc: usb@freebsd.org Subject: Re: USB2 - umass problem X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Feb 2009 10:24:56 -0000 On Wednesday 04 February 2009, Vladimir Grebenschikov wrote: > On Wed, 2009-02-04 at 10:44 +0100, Hans Petter Selasky wrote: > > > By some reason devfs semantic was changed: > > > Instead of /dev/cuaU0.[0-2] and /dev/ttyU0.[0-2], I've get > > > /dev/cuaU[0-2] /dev/ttyU[0-2] and! /dev/cuau1 /dev/ttyu1 > > > What is reason for such change (additional port with lowercase 'u' and > > > U[0-2] instead of more logical U0.[0-2]) ? > > > > It is because we are attaching drivers per interface instead of per > > device. A new modem unit is allocated every time we find a modem, simply > > put. If the modem has multiple instances in an interface, > > /dev/cuaU0.[0...] will be created. Else /dev/cuaU... . > > What about /dev/cuau1 /dev/ttyu1 ? TTYs follow the same naming convention like the cuaUxx . If the modem has got one modem in each interface and three interfaces: /dev/cuaU0 /dev/ttyU0 /dev/cuaU1 /dev/ttyU1 /dev/cuaU2 /dev/ttyU2 If the modem has got three modems in one interface: /dev/cuaU0.0 /dev/ttyU0.0 /dev/cuaU0.1 /dev/ttyU0.1 /dev/cuaU0.2 /dev/ttyU0.2 How this is configured is decided by the USB device manufacturer. --HPS