From owner-freebsd-usb@FreeBSD.ORG Sat May 23 12:25:45 2015 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 755F94A9 for ; Sat, 23 May 2015 12:25:45 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 09E2119F7 for ; Sat, 23 May 2015 12:25:44 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id t4NCPP9s008042 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 23 May 2015 14:25:26 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id t4NCPNYV048473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 23 May 2015 14:25:23 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id t4NCPNAW055407; Sat, 23 May 2015 14:25:23 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id t4NCPNlB055406; Sat, 23 May 2015 14:25:23 +0200 (CEST) (envelope-from ticso) Date: Sat, 23 May 2015 14:25:23 +0200 From: Bernd Walter To: Gary Jennejohn Cc: Bernd Walter , freebsd-usb@freebsd.org Subject: Re: High-Speed devices listed at XHCI Message-ID: <20150523122522.GH51052@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20150522234257.GD51052@cicely7.cicely.de> <20150523093621.0da6caa6@ernst.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150523093621.0da6caa6@ernst.home> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2015 12:25:45 -0000 On Sat, May 23, 2015 at 09:36:21AM +0200, Gary Jennejohn wrote: > On Sat, 23 May 2015 01:42:57 +0200 > Bernd Walter wrote: > > > I'm a bit confused, because so far I'd thought that SS USB Hub > > topology means that HS/FS/LS is a separate structure sharing the same > > connector as SS. > > Now, just a few minutes ago I've added a beafy SS hub with 16 ports > > (actually 4 port => 4x4 Port in one case) to my system to migrate disks > > from HS ports to SS, but also connected HS drives to the SS ports. > > I see all SS hubs twice, as SS and HS hubs, which is understandable with > > the dual topology, but they are all listed at the XHCI controller and > > also use 2 addresses on the XHCI. > > Also the HS devices (or the single SS device with HS only-cable) are > > listed at the XHCI. > > > > [63]cicely1# usbconfig > > ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) > > ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) > > ugen2.1: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) > > ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) > > ugen2.2: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) > > ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA) > > ugen0.3: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA) > > ugen0.4: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA) > > ugen0.5: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA) > > ugen0.6: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA) > > ugen0.7: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) > > ugen0.8: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) > > ugen0.9: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (36mA) > > ugen0.10: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (36mA) > > ugen0.11: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (36mA) > > ugen0.12: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (36mA) > > ugen0.13: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) > > ugen0.14: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (36mA) > > ugen0.15: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (36mA) > > ugen0.16: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) > > ugen0.17: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) > > ugen0.18: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (0mA) > > ugen0.19: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (0mA) > > ugen0.20: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (0mA) > > ugen0.21: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (0mA) > > ugen0.22: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (2mA) > > ugen0.23: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (2mA) > > ugen0.24: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) > > ugen0.25: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) > > ugen0.26: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) > > > > Yeah, but they have to be different endpoints on the XHCI controller > to reflect the SS/HS difference. I'm not surprised to see them listed twice, but that they are both listed at the XHCI. So the XHCI also does the HS job? I would have expected the SS to be on the XHCI and HS on an EHCI. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.