From owner-freebsd-bluetooth@FreeBSD.ORG Tue Mar 27 19:13:33 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 807FA16A402 for ; Tue, 27 Mar 2007 19:13:33 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smarthost01.eng.net (smarthost01.eng.net [213.130.146.173]) by mx1.freebsd.org (Postfix) with ESMTP id 3E28A13C459 for ; Tue, 27 Mar 2007 19:13:33 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from netmail01.eng.net ([213.130.128.38] helo=rya-online.net) by smarthost01.eng.net with smtp (Exim 4.62) (envelope-from ) id 1HWH6j-0003Uc-Ne; Tue, 27 Mar 2007 20:13:30 +0100 Received: (nullmailer pid 15211 invoked by uid 1000); Tue, 27 Mar 2007 18:37:50 -0000 Date: Tue, 27 Mar 2007 19:37:50 +0100 (BST) To: Deniss Lee In-Reply-To: <938b57eb0703270634x664fde21l422703ba48ebbd3c@mail.gmail.com> References: <938b57eb0703270634x664fde21l422703ba48ebbd3c@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1175020670.210606.27229.nullmailer@galant.ukfsn.org> From: Iain Hibbert Cc: freebsd-bluetooth@freebsd.org Subject: Re: bluetooth dongle not working X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2007 19:13:33 -0000 On Tue, 27 Mar 2007, Deniss Lee wrote: > > > you did not provide enough details to give you any useful answer. just > > > by looking at the error message i can say that your bluetooth dongle > > > did not respond to the "reset" command. > > > > This sounds similar to a problem that occurred on the NetBSD (USB) stack, > > when the USB was ehci->uhci->ubt - maybe Deniss can post the relevant > > parts of his dmesg? > What was solution to that NetBSD problem you just described? The problem was something to do with "data toggles" in the EHCI code - see http://cvsweb.netbsd.org (I think), look in src/sys/dev/usb/ehci.c and it was fixed a couple of months ago (by Matthias Drochner) more than one person was seeing the exact same thing - the first packet sent on the control endpoint (a command) would generate data on the interrupt endpoint (an event) but the second would not, and thus the 'dongle did not respond' error sounds familiar.. I don't know if the same problem exists on FreeBSD (it was the same USB stack though has had different fixes applied over time), and IIRC the FreeBSD ng_ubt driver handles the USB interrupt transfers slightly differently, so it could be unrelated, but its worth a try.. iain