Hi Marcel, On 06/30/15 07:05, Sumit's Mailing Lists wrote: > Ben, > > Kvalo updated the wl-ath+ kernel fork to 4.1.0 so I attempted this again > to see if it might have been a bug that's been fixed. > > So I'm using https://github.com/kvalo/ath commit > 916a6fc66cc013dd67af0d5da546be0012ac2b2c > > with the following patch: > > diff --git a/drivers/bluetooth/Makefile b/drivers/bluetooth/Makefile > index f40e194..35fee06 100644 > --- a/drivers/bluetooth/Makefile > +++ b/drivers/bluetooth/Makefile > @@ -1,6 +1,7 @@ > # > # Makefile for the Linux Bluetooth HCI device drivers. > # > +CFLAGS_btusb.o := -DDEBUG > > obj-$(CONFIG_BT_HCIVHCI) += hci_vhci.o > obj-$(CONFIG_BT_HCIUART) += hci_uart.o > diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c > index 94c6c04..1c476d8 100644 > --- a/drivers/bluetooth/btusb.c > +++ b/drivers/bluetooth/btusb.c > @@ -194,7 +194,6 @@ static const struct usb_device_id blacklist_table[] = { > { USB_DEVICE(0x0930, 0x0227), .driver_info = BTUSB_ATH3012 }, > { USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 }, > { USB_DEVICE(0x0cf3, 0x0036), .driver_info = BTUSB_ATH3012 }, > - { USB_DEVICE(0x0cf3, 0x3004), .driver_info = BTUSB_ATH3012 }, > { USB_DEVICE(0x0cf3, 0x3008), .driver_info = BTUSB_ATH3012 }, > { USB_DEVICE(0x0cf3, 0x311d), .driver_info = BTUSB_ATH3012 }, > { USB_DEVICE(0x0cf3, 0x311e), .driver_info = BTUSB_ATH3012 }, > @@ -224,6 +223,7 @@ static const struct usb_device_id blacklist_table[] = { > { USB_DEVICE(0x0cf3, 0xe007), .driver_info = BTUSB_QCA_ROME }, > { USB_DEVICE(0x0cf3, 0xe300), .driver_info = BTUSB_QCA_ROME }, > { USB_DEVICE(0x0cf3, 0xe360), .driver_info = BTUSB_QCA_ROME }, > + { USB_DEVICE(0x0cf3, 0x3004), .driver_info = BTUSB_QCA_ROME }, > > /* Broadcom BCM2035 */ > { USB_DEVICE(0x0a5c, 0x2009), .driver_info = BTUSB_BCM92035 }, > > > I rebooted into linux-4.1.0-wl-ath+ and the very first command I ran was > "hciconfig hci0 up" and I still get the following in my kernel logs: > > [ 30.011420] hci0 > [ 30.011439] Bluetooth: hci0: Failed to access otp area (-113) > > Here is my full kernel log: https://bpaste.net/show/96c4d5571356 > > Sumit > > According to log, looks like patch download was done in btusb_open function, however, btusb_open was not completed after QCA patching steps were going through I believe. [ 6.505349] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00000200.bin [ 6.505352] Bluetooth: hci0: QCA: patch rome 0x200 build 0x299, firmware rome 0x200 build 0x111 [ 6.558661] Bluetooth: hci0: using NVM file: qca/nvm_usb_00000200.bin ... [ 9.133753] hci0 urb ffff8800c9cbba80 status -2 count 0 [ 9.134085] hci0 urb ffff8800c9cbb9c0 status -2 count 0 [ 9.134377] hci0 urb ffff8800c9cbb300 status -2 count 0 The status -2 means urb->status(-ENOENT). Haven you seen this error during sequences of btusb_open function? Could you give me some insight why we're getting -ENOENT error after patching is done? Hi Sumit, I'm expecting your card is up and running properly on Windows to make sure there is NO HW problem. Can you please double confirm? Addition to that, does WLAN(ath10k) work on your laptop? Thanks -- Ben Kim -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
