Well hci_ll is tied up with hci_ldisc, we might not even want BT/FM on system, may be just GPS (like we have for 1 version of chip).
In that case GPS directly uses the ST line discipline.
Correct, However that piece of Android code, as far as I have seen it depends on bunch of interfaces provided by the UART driver.
The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/
that is what I am saying. Lets take the hci_ll driver out of it and
create some sort of LL subsystem. Then the TI Bluetooth driver just uses
LL and doesn't have to use hci_ldisc framework.
Don't be afraid of taking hci_ll out of the Bluetooth part and make it a
I don't see a problem with it in general. However having some more
That sounds just like an excuse. We should be able to abstract this
If possible please share some more details about the protocol in use and
the platform architecture of the chip. I think you are trying to make
this more complicated than it has to be.