Boki
Guest
Wed Jun 23, 2010 6:19 pm
Hi All,
When a SW engineer change their Bluetooth solution ( ex: from CSR to
TI, or vice versa ), what's the main effort it needs ? assume based on
Android end-product.
The only stuff in my mind is porting driver ( assume BT stack is
available, ex: BlueZ )
so, it is only few effort on the Bluetooth chip initialization,
right ?
I think in current market, all bluetooth chips should supporting UART,
and up to 4Mbps, right ?
Thanks.
Boki.
JosephKK
Guest
Thu Jul 01, 2010 4:35 pm
On Wed, 23 Jun 2010 08:19:10 -0700 (PDT), Boki <boki.digital_at_gmail.com>
wrote:
Quote:
Hi All,
When a SW engineer change their Bluetooth solution ( ex: from CSR to
TI, or vice versa ), what's the main effort it needs ? assume based on
Android end-product.
The only stuff in my mind is porting driver ( assume BT stack is
available, ex: BlueZ )
so, it is only few effort on the Bluetooth chip initialization,
right ?
I think in current market, all bluetooth chips should supporting UART,
and up to 4Mbps, right ?
Thanks.
Boki.
Ooo. Too many assumptions there. Make them back it up.
