On Tue, Oct 27, 2015 at 1:02 PM, John Salatas <jsalatas@xxxxxxxxx> wrote: > On Tue, Oct 27, 2015 at 12:52 PM, John Salatas <jsalatas@xxxxxxxxx> wrote: >> ... >> I'm guessing that it needs some kind of firmware in order to work. As >> it seems to me (based on >> https://wireless.wiki.kernel.org/en/users/drivers/ath3k#how_to_tell_ar3011_and_ar3012) >> this is an AR3011 device, and so I added it's id in ath3k.c and >> btusb.c in a similar way as here: >> http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=6eda541d12116b4772baa09d3e8d7b0389df4289 >> >> After rebooting, I didn't get any errors in dmesg but the device is >> not recognised at all know. Eg rfkill list gives the following >> 0: acer-wireless: Wireless LAN >> Soft blocked: no >> Hard blocked: no >> 2: phy0: Wireless LAN >> Soft blocked: no >> Hard blocked: no >> 3: hci0: Bluetooth >> Soft blocked: no >> Hard blocked: no >> >> It doesn't work any more even if I do the attach to VM trick. >> .... > > Ooops, sorry wrong copy/paste. actually after adding it's id in > ath3k.c and btusb.c and rebooting rfkill list gives the following > > 0: acer-wireless: Wireless LAN > Soft blocked: no > Hard blocked: no > 2: phy0: Wireless LAN > Soft blocked: no > Hard blocked: no > Just replying to this in case it got lost in the mailing list. I would appreciate any feedback. Thanks again! -- 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
