From owner-freebsd-usb@FreeBSD.ORG Sat Jul 23 21:49:40 2011 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 495BC106566C for ; Sat, 23 Jul 2011 21:49:40 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.c2i.net [212.247.154.66]) by mx1.freebsd.org (Postfix) with ESMTP id C28488FC08 for ; Sat, 23 Jul 2011 21:49:39 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=EIZfbDsN8gr1c4B7uGrP4foh/gtfZ6zZRee2cLtKwTU= c=1 sm=1 a=SvYTsOw2Z4kA:10 a=fa5KVJVg6bUA:10 a=WQU8e4WWZSUA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=8kQB0OdkAAAA:8 a=k8-pEbd4mNSnOSzNDd8A:9 a=wPNLvfGTeEIA:10 a=9aOQ2cSd83gA:10 a=CEmdd8RweNuGuMQs:21 a=S_rV1JvW8pfOGQ_4:21 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe03.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 156525334; Sat, 23 Jul 2011 23:49:37 +0200 From: Hans Petter Selasky To: Peer Stritzinger Date: Sat, 23 Jul 2011 23:47:22 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: <201107231755.23755.hselasky@c2i.net> In-Reply-To: X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq,NwSZ4V" =?iso-8859-1?q?=7CLR=2E+tj=7Dg5=0A=09=25V?=,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( =?iso-8859-1?q?=0A=09=3AAuzV9=3A=2EhESm-x4h240C=609=3Dw?= MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201107232347.22310.hselasky@c2i.net> Cc: freebsd-usb Subject: Re: Powercycling USB device on hub 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: Sat, 23 Jul 2011 21:49:40 -0000 On Saturday 23 July 2011 18:53:46 Peer Stritzinger wrote: > On Sat, Jul 23, 2011 at 5:55 PM, Hans Petter Selasky wrote: > >> Since power-cycling needs to reset the HUB I now have the problem to > >> find out on which HUB in the system my device hangs. > >> > >> There are two HUB's on the same root HUB and I don't want to > >> power-cycle all devices. Is there a way to learn the physical > >> structure of a USB bus? > > > > devinfo > > > > Address 1 is always the root HUB. > > Tried this already but it only shows the hubs but none of my devices > because they have no driver (custom built USB devices, only talk to > them via libusb). > > e.g. > > usbus3 > uhub3 > uhub4 pnpinfo vendor=0x0424 product=0x2514 devclass=0x09 > devsubclass=0x00 sernum="" release=0x0bb3 intclass=0x09 > intsubclass=0x00 at port=7 interface=0 > uhub5 pnpinfo vendor=0x0424 product=0x2514 devclass=0x09 > devsubclass=0x00 sernum="" release=0x0bb3 intclass=0x09 > intsubclass=0x00 at port=8 interface=0 > > There is one of the devices attached either to uhub4 or uhub5 (visible > in usbconfig) but nothing shown in devinfo (even with -v). > > -- Peer In newer libusb there is a function to get the parent HUB address. --HPS