After some testing on a few laptops it looks like the firmware loads always
correctly only using AR3012 variant.
So the correct patch follows
---
diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
index d85ced2..086240c 100644
--- a/drivers/bluetooth/ath3k.c
+++ b/drivers/blueto
It seems that I am too stupid.
It is neither AR3012 or AR3011 device.
It is AR9565 with sflash.
Probably it makes sense to do a separate section for these devices.
But still
{ USB_DEVICE(0x13d3, 0x3408), .driver_info = BTUSB_IGNORE },
works better than
{ USB_DEVICE(0x13d3, 0x3408), .driver_info
Hi Michael,
As I understood it is a combined device with BT and Wi-Fi WB335 ( based
on AR9565 )
It has MCI bt chip.
http://wireless.kernel.org/en/users/Drivers/ath9k/btcoex
http://wireless.kernel.org/en/users/Drivers/ath3k
But still ath3k firmware is needed.
I am just confused if it is AR3011
Hi,
I tried to understand why this "0x13d3, 0x3408" device support
wouldn't go in btusb as it's really close to IMC BT chip found in
Realtek Wifi devices which is on the path to go in btusb [1]
then I guess there is a lot of code that could be shared to support
all IMC usb devices in the btusb mo
Hi Marcel,
Here is information from /sys/kernel/debug/usb/devices
T: Bus=01 Lev=02 Prnt=03 Port=00 Cnt=01 Dev#= 20 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=13d3 ProdID=3408 Rev= 0.02
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
A: FirstIf#= 0 IfCount= 2 C
5 matches
Mail list logo
