Date: Tue, 27 Mar 2007 19:37:50 +0100 (BST) From: Iain Hibbert <plunky@rya-online.net> To: Deniss Lee <deniss.lee@gmail.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: bluetooth dongle not working Message-ID: <1175020670.210606.27229.nullmailer@galant.ukfsn.org> In-Reply-To: <938b57eb0703270634x664fde21l422703ba48ebbd3c@mail.gmail.com> References: <938b57eb0703270634x664fde21l422703ba48ebbd3c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1175020670.210606.27229.nullmailer>