well what if the FM core now understands that the hci-vs commands ? There was bsp interface [i2c complaint] earlier - now if suppose the firmware is able to interpret hci-vs commands ?
and my application would then do socket (on hci0) then use hci_send_cmd or hci_send_req to send fm control commands ? and all interrupts [earlier] from chip now comes in as hci-command complete events ? -- also please point me to your blog/comments regards, Pavan On Thu, Aug 27, 2009 at 11:58 AM, Erin Yueh <eriny...@gmail.com> wrote: > > Hi Pavan, > > On Aug 27, 12:49 pm, pavan savoy <pavan.sa...@gmail.com> wrote: > > Hi, > > > > Yes - my question kind of lost its purpose somewhere in between. > > All I wanted to know is how the BT & FM share the UART ? > > > > I have android UI recognize the BT core below - however If I wanted to > > develop an FM application and use it - I am stuck with trying to turn on > BT > > when I want to use the FM application because my FM jni is talking > > hci-vendor specific commands instead of some i2c sort of commads. > > > > Note: I don't have a platform yet. But know for sure that the bt + fm > chip > > is interfaced to the apps processor over uart. > > > > > > I am not sure whether it is true or not. I saw a comment in my blog > and it's > said there is an issue about this chip. UART is occupied by Bluez when > BT is > on so we cannot control FM when BT is on. You probably could check > this issue > first. > > Regards, > Erin Yueh > http://0xlab.org/ > > > > [...] > > > > -- --Pavan Savoy --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
