From owner-freebsd-current@FreeBSD.ORG Thu Dec 25 00:37:10 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CF99106564A for ; Thu, 25 Dec 2008 00:37:10 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 8648C8FC17 for ; Thu, 25 Dec 2008 00:37:10 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 706401A3C3A; Wed, 24 Dec 2008 16:37:10 -0800 (PST) Date: Wed, 24 Dec 2008 16:37:10 -0800 From: Alfred Perlstein To: Giorgos Keramidas Message-ID: <20081225003710.GD18389@elvis.mu.org> References: <20081222214010.GA18389@elvis.mu.org> <20081224215330.3ccc613d@gluon> <874p0t2iyw.fsf_-_@kobe.laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <874p0t2iyw.fsf_-_@kobe.laptop> User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org, Hans Petter Selasky Subject: Re: Tracking the open USB2 issues? 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: Thu, 25 Dec 2008 00:37:10 -0000 * Giorgos Keramidas [081224 16:33] wrote: > Just picking one random email in the usb threads to reply to... > > Do we keep a list of open issues with the new USB stack somewhere? > > Should we record the ones reported in -current somewhere, so they don't > get lost? A simple plain text file like src/UPDATING may be enough to > keep a log of the already reported issues. A special 'usb' category of > PRs in Gnats may be ok too. Anything that makes it easy to go through a > list of reported problems, check how many of them are fixed, and export > a list of stuff that we should fix later is going to be immensely useful > when we get very near 8.0-RELEASE. Let's do a gnats catagory. Anything special I have to do to add a "newusb" catagory? thanks, -Alfred > > On Wed, 24 Dec 2008 21:53:30 +0000, Bruce Cran wrote: > > I've found a few issues when testing my OpenMoko phone with the > > new stack. > > > > I know this has already been reported > > (http://lists.freebsd.org/pipermail/freebsd-usb/2008-September/005462.html) > > but I'd expect that loading usb2_ethernet_cdce would make the phone > > attach as a CDCE device, but it still attaches using ugen. I don't > > know if this is possible but could the usb stack automatically use > > config 1 when it attaches, knowing that RNDIS (config 0) isn't > > supported yet? > > > > I also noticed that usbconfig(8) refers to usb2_core(4) which doesn't > > exist. > > > > Something strange is going on with one of my USB ports. A CSR > > Bluetooth dongle gets detected, but nothing else plugged in does. > > > > usbconfig list: > > [...] > > ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) > > pwr=ON > > [...] > > ugen2.2: at usbus2, > > cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > > > > Could this be because the CSR device is a FULL-speed device but > > everything else I have (a Broadcom EDR dongle, flash drive and an > > OpenMoko phone) are all HIGH-speed devices? > > > > If usbconfig needs root privileges to work, it should say so. It > > currently reports "No device match" when it should probably say that > > the current user isn't root, to avoid confusion. > > > > Should usbconfig(8) document the commands? > > > > Finally, ugen devices don't report being unplugged - I'd expect to be > > told that the device has gone away. > > -- -- - Alfred Perlstein