Fabien<br><br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Brad's questions brings up even some more questions. Brad is talking<br>
about a2dp which should really be cool to have on OpenMoko </blockquote><div><br>voice is obviously more relevant first.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Some other questions that i would be very happy to have answers for :<br> * Which bluetooth chip will you use? Which version (1.2 or 2.0 ?)</blockquote><div><br>it's also worth asking if neo will use the pcm path direct from the bluetooth chip or if they will move audio across hci. If they're using pcm that would explain why we haven't heard of it since most of our driver work is dealing with hci audio.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> * Which profiles to you intend to support in the initial release ?</blockquote>
</div><br>I took it for a given that bt voice was going to be somehow supported but maybe not.<br><br>Brad<br>