From owner-freebsd-current@FreeBSD.ORG Mon Feb 16 18:42:35 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F25A71065677; Mon, 16 Feb 2009 18:42:34 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from pele.citylink.co.nz (pele.citylink.co.nz [202.8.44.226]) by mx1.freebsd.org (Postfix) with ESMTP id 8957B8FC08; Mon, 16 Feb 2009 18:42:34 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by pele.citylink.co.nz (Postfix) with ESMTP id D1219FF32; Tue, 17 Feb 2009 07:42:33 +1300 (NZDT) X-Virus-Scanned: Debian amavisd-new at citylink.co.nz Received: from pele.citylink.co.nz ([127.0.0.1]) by localhost (pele.citylink.co.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YhSLPm+JF9iy; Tue, 17 Feb 2009 07:42:30 +1300 (NZDT) Received: from citylink.fud.org.nz (unknown [202.8.44.45]) by pele.citylink.co.nz (Postfix) with ESMTP; Tue, 17 Feb 2009 07:42:30 +1300 (NZDT) Received: by citylink.fud.org.nz (Postfix, from userid 1001) id C123B1142F; Tue, 17 Feb 2009 07:42:29 +1300 (NZDT) Date: Mon, 16 Feb 2009 10:42:29 -0800 From: Andrew Thompson To: Maksim Yevmenkin Message-ID: <20090216184229.GA12555@citylink.fud.org.nz> References: <87mycme9wc.fsf@kobe.laptop> <200902161752.56998.hselasky@freebsd.org> <87wsbqmeq4.fsf@kobe.laptop> <200902161930.25235.hselasky@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-current@freebsd.org, Hans Petter Selasky , Giorgos Keramidas Subject: Re: usb2 moused issue X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 18:42:35 -0000 On Mon, Feb 16, 2009 at 10:41:19AM -0800, Maksim Yevmenkin wrote: > On Mon, Feb 16, 2009 at 10:30 AM, Hans Petter Selasky > wrote: > > The device is invisible. You should be able to cat it, if it's not already > > opened. > > yeah, i've been bitten by the same "invisible device node" problem > while converting ubtbcmfw(4) to usb2. for example, > > Feb 16 10:35:19 yak kernel: ugen0.2: at usbus0 > Feb 16 10:35:19 yak kernel: ubtbcmfw0: dongle, class 224/1, rev 1.01/0.a0, addr 2> on usbus0 > Feb 16 10:35:19 yak kernel: Symlink: ubtbcmfw0 -> usb0.2.0.16 > Feb 16 10:35:19 yak kernel: Symlink: ubtbcmfw0.1 -> usb0.2.0.16 > Feb 16 10:35:19 yak kernel: Symlink: ubtbcmfw0.2 -> usb0.2.0.16 > > and > > > pwd > /dev > > > ls -la usb0.2.* > ls: No match. > > ls -la usb0.2.0.16 > crwxrwxrwx 1 root operator 0, 68 Feb 5 10:19 usb0.2.0.16 > > > ls -la ubtbcmfw* > ls: No match. > > ls -la ubtbcmfw0 > crwxrwxrwx 1 root operator 0, 68 Feb 5 10:19 ubtbcmfw0 > > > ls -la ubtbcmfw0.* > ls: No match. > > > ls -la ubtbcmfw0.1 > crwxrwxrwx 1 root operator 0, 68 Feb 5 10:19 ubtbcmfw0.1 > > ls -la ubtbcmfw0.2 > crwxrwxrwx 1 root operator 0, 68 Feb 5 10:19 ubtbcmfw0.2 > > i suspect it probably has something to do with the way devfs cloning > works (for example, i think, somewhat similar problem exists with > /dev/tap, /dev/tun device nodes). of course, if one does not know > that, the first reaction would be - wtf? where is my device nodes?! :) > > i wonder if there is any way to "fix" it... A fix is in progress. Andrew