From owner-freebsd-usb@FreeBSD.ORG Fri Aug 26 11:52:57 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 D0123106564A; Fri, 26 Aug 2011 11:52:57 +0000 (UTC) (envelope-from kraxel@redhat.com) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mx1.freebsd.org (Postfix) with ESMTP id AD1368FC08; Fri, 26 Aug 2011 11:52:57 +0000 (UTC) Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p7QBqvSM016635 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 26 Aug 2011 07:52:57 -0400 Received: from rincewind.home.kraxel.org (ovpn-116-18.ams2.redhat.com [10.36.116.18]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p7QBqsfV025875; Fri, 26 Aug 2011 07:52:55 -0400 Message-ID: <4E578916.1050509@redhat.com> Date: Fri, 26 Aug 2011 13:52:54 +0200 From: Gerd Hoffmann User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Red Hat/3.1.12-1.el6_1 Thunderbird/3.1.12 MIME-Version: 1.0 To: Juergen Lock References: <20110815202656.GA94934@triton8.kn-bremen.de> <4E577890.5030200@redhat.com> In-Reply-To: <4E577890.5030200@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23 Cc: freebsd-emulation@FreeBSD.org, hselasky@FreeBSD.org, freebsd-usb@FreeBSD.org, qemu-devel@nongnu.org Subject: Re: [Qemu-devel] qemu 0.15.0 testing, usb redirection, and libusb_get_device_speed() 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: Fri, 26 Aug 2011 11:52:57 -0000 Hi, > /me wonders what FreeBSD tries to do here? This triggers even without a > single device connected and I can't think of a reason to use a siTD in > that case ... Ah, the siTD simply isn't active so we can just skip it. That is easy to do ;) cheers, Gerd