https://bugzilla.kernel.org/show_bug.cgi?id=58481 --- Comment #6 from Tobias Jakobi <liquid.acid@xxxxxxx> 2013-05-23 13:20:57 --- (In reply to comment #5) > It looks like you are not getting a response to the HCI command sent to the > wilink chip over UART. > Can you make sure that the BT_Enable pin is also muxed correctly and you see it > "high" when UART conversation starts? How would I do that? I can very well read the kernel sourcecode, but I know nothing about UART programming and stuff. > Anyway for 3.9 the right thing to do would be to switch to using DT, however > device tree support is still missing for the ti-st and btwilink driver and the > device tree bindings for kim and btwilink are not yet in the .dtb files I tried DT, but as you can see in bug #58611 it currently doesn't work for me, even with the 3.10 release candidate. But if I understand you correctly, in the current situation DT wouldn't really help me. > I have just made the modifications to ti-st and btwilink and got bluetooth to > work for omap5-uevm, but this is no up-streamed yet. If you have some patches for the panda-es, I would be happy to test them! Greets, Tobias -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- 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
