From owner-freebsd-current@FreeBSD.ORG Wed Oct 13 07:10:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F4B416A4D1 for ; Wed, 13 Oct 2004 07:10:53 +0000 (GMT) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DA2843D39 for ; Wed, 13 Oct 2004 07:10:51 +0000 (GMT) (envelope-from avg@icyb.net.ua) Received: from [212.40.38.87] (oddity.topspin.kiev.ua [212.40.38.87]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA05765; Wed, 13 Oct 2004 10:10:41 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <416CD4F1.5050300@icyb.net.ua> Date: Wed, 13 Oct 2004 10:10:41 +0300 From: Andriy Gapon User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040831) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ian Dowse References: <1097623381.00149000.1097610001@10.7.7.3> In-Reply-To: <1097623381.00149000.1097610001@10.7.7.3> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 13 Oct 2004 12:04:27 +0000 cc: current@freebsd.org Subject: Re: Are USB 2 hubs supported in FreeBSD 5.3? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 13 Oct 2004 07:10:53 -0000 on 12.10.2004 22:38 Ian Dowse said the following: ... > Actually, USB2 hubs should now work well enough to talk to USB2 > devices (they work for me connecting USB2 umass devices anyway), > but we don't have support for talking to USB1 devices via USB2 hubs > yet. ... I had experience to the contrary with 5.2.1: http://www.freebsd.org/cgi/getmsg.cgi?fetch=24565+28404+/usr/local/www/db/text/2004/freebsd-hardware/20040926.freebsd-hardware Btw, I had actually tried to use the latest sys/dev/usb/ehci* files from CVS with the rest of 5.2.1 files (backing out only bus_alloc_resource_any() change) and I had exactly the same problem, so it seems that either this problem is not fixed in CURRENT or the problem is not local to ehci code e.g. it is in umass/ehci interaction. -- Andriy Gapon