From owner-freebsd-current@FreeBSD.ORG Tue May 19 06:51:45 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 5A07B106564A; Tue, 19 May 2009 06:51:45 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe16.tele2.se [212.247.155.225]) by mx1.freebsd.org (Postfix) with ESMTP id 898578FC08; Tue, 19 May 2009 06:51:44 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=bvA9ArPTLE4A:10 a=wUE4w7GWRSwA:10 a=j+k/Ze5hWUCaCztCgEjzDQ==:17 a=5zm0jQc0V6eMfDCqFC0A:9 a=pBpX1mZlgZ7NZOZMHouGml9Aw6QA:4 Received: from [81.191.55.181] (account mc467741@c2i.net HELO laptop) by mailfe16.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 500290261; Tue, 19 May 2009 08:51:42 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Tue, 19 May 2009 08:54:17 +0200 User-Agent: KMail/1.9.7 References: <20090407022956.GA71377@weongyo.cdnetworks.kr> <20090519050132.GE42412@weongyo.cdnetworks.kr> <20090519051045.GD78829@citylink.fud.org.nz> In-Reply-To: <20090519051045.GD78829@citylink.fud.org.nz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905190854.17888.hselasky@c2i.net> Cc: Lucius Windschuh , Sam Leffler , Andrew Thompson Subject: Re: HEADSUP: uath(4) has been committed. 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: Tue, 19 May 2009 06:51:45 -0000 On Tuesday 19 May 2009, Andrew Thompson wrote: > On Tue, May 19, 2009 at 02:01:32PM +0900, Weongyo Jeong wrote: > > > > BTW: Could you add a message declaring the device when it is plugged > > > > in? Something like "uath0: > > > > on usbus?" and "uath0: ether aa:bb:cc:dd:ee:ff"? > > > > > > I thought it did this but perhaps not; we can try to add it. > > > > IIRC in the previous USB1, it printed a message like > > > > uath0: on usbus? > > > > whenever a device is attached even if the device source doesn't print > > it but it's not now in USB2. I have no ideas it's a intention or a > > regression of USB2. > > This is because USB2 sets the quiet flag on the device (for better or > worse) and relies on the driver calling device_set_usb2_desc(). > > I am not sure the reason for doing it this way. > Did you run uathload? There should be an ugen entry for your device. --HPS