Hi Sagar, >> Just an note that recent backports dropped support for kernels older than 3.0. >> So some older release might be needed for 2.6.37. >> > I have managed to backport it thanks. > > > But bluetoothctl doesnt detect it, It says the following: > > # bluetoothctl > [bluetooth]# power on > No default controller available > [bluetooth]# you need a running bluetoothd for bluetoothctl. > Here is output of hciconfig: > > $ hciconfig -a > hci0: Type: BR/EDR Bus: UART > BD Address: 34:B1:F7:E2:DE:CB ACL MTU: 1021:6 SCO MTU: 180:4 > UP RUNNING PSCAN ISCAN > RX bytes:12525 acl:56 sco:0 events:262 errors:0 > TX bytes:2948 acl:52 sco:0 commands:108 errors:0 > Features: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87 > Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 > Link policy: RSWITCH HOLD SNIFF > Link mode: SLAVE ACCEPT > Name: 'bt_hw' > Class: 0x001f00 > Service Classes: Unspecified > Device Class: Invalid Device Class! > HCI Version: 4.1 (0x7) Revision: 0x0 > LMP Version: 4.1 (0x7) Subversion: 0xac7c > Manufacturer: Texas Instruments Inc. (13) > > # Just our of curiosity, does this chip support BR/EDR Secure Connections? You might need to check with hciconfig hci0 features or run btmon to see the fully decoded list. > And I scan devices using hcitool as well. > > Any pointers why bluetoothctl fails ? btmgmt, hciconfig etc. operate on the kernel level interfaces. Which you normally use for testing or development. For everything else, run bluetoothd and then bluetoothctl will work. Regards Marcel -- 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
