Re: [PATCH] Bluetooth: Add support for Atheros [0cf3:e004]

Dear Marcel,

I just verified that, on 3.0 kernel, the btusb will be loaded after
ath3k. That will lead to the problem.

But, on 3.2 kernel, btusb will be loaded before ath3k.
And I forced it to load ath3k before btusb on 3.2 kernel, and it works
as expected.
So, there is no loading order issue on 3.2 kernel.

I removed the wording about the module loading order and reattach it again.

Best regards,
AceLan Kao.

2012/1/31 Marcel Holtmann [off-list ref]:

Hi AceLan,

quoted

Add another vendor specific ID for Atheros BT device

output of usb-devices:
T:  Bus=02 Lev=02 Prnt=02 Port=04 Cnt=01 Dev#=  4 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0cf3 ProdID=e004 Rev=00.02
S:  Manufacturer=Atheros Communications
S:  Product=Bluetooth USB Host Controller
S:  SerialNumber=Alaska Day 2006
C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

BTW, to enable this device correctly, the btusb module should be loaded
before ath3k. So, user should have this line in /etc/modprobe.d/ath3k.conf

   install ath3k modprobe btusb; modprobe --ignore-install ath3k;

NAK. Get this fixed properly then.

Regards

Marcel

-- 
Chia-Lin Kao(AceLan)
http://blog.acelan.idv.tw/
E-Mail: acelan.kaoATcanonical.com (s/AT/@/)