On Thu, 2011-07-28 at 04:33 -0400, Eponymous - wrote: > Thanks for your reply Peter. > > The problem I've got is that I work for a company testing Bluetooth so > I have my hands tied as to how much information I can give - this is > obviously a nightmare for both you who is trying to help me and for me > who is trying to get the issue fixed :) > > It could be very well that the program I'm using (that used to work > with BlueZ just fine when the hci_usb driver was around) is no longer > compatible. > > I need to speak to the developers of the program I'm using to work out > how they communicate with BlueZ/the chip. > > Cheers. Hi, The patch to the btusb driver (which may or may not fix the issue you're having) is on the bluetooth-next development tree and is slated for inclusion in the next kernel release (probably sometime in September, based on current release cycle times). If your familiar with how to build a kernel module, you could grab the patch from this list here: http://permalink.gmane.org/gmane.linux.bluez.kernel/14758 Then rebuild 'drivers/bluetooth/btusb'. Let us know whether or not that resolves the problem. Regards, Peter ��.n��������+%������w��{.n�����{��� �^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
